#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
d678a59d |
|
18-May-2024 |
Tom Rini <trini@konsulko.com> |
Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"" When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"' I failed to notice that b4 noticed it was based on next and so took that as the base commit and merged that part of next to master. This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35. Reported-by: Jonas Karlman <jonas@kwiboo.se> Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
1227a30d |
|
01-May-2024 |
Tom Rini <trini@konsulko.com> |
api: Remove <common.h> and add needed includes Remove <common.h> from here and when needed add missing include files directly. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
b630f8b3 |
|
27-Oct-2023 |
Tom Rini <trini@konsulko.com> |
scsi: Forceably finish migration to DM_SCSI The migration deadline for moving to DM_SCSI was v2023.04. A further reminder was sent out in August 2023 to the remaining platforms that had not migrated already, and that a few more over the line (or configs deleted). With this commit we: - Rename CONFIG_DM_SCSI to CONFIG_SCSI. - Remove all of the non-DM SCSI code. This includes removing other legacy symbols and code and removes some legacy non-DM AHCI code. - Some platforms that had previously been DM_SCSI=y && SCSI=n are now fully migrated to DM_SCSI as a few corner cases in the code assumed DM_SCSI=y meant SCSI=y. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
9ba938e7 |
|
28-Oct-2022 |
Tom Rini <trini@konsulko.com> |
Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig This converts the following to Kconfig: CONFIG_SYS_MMC_MAX_DEVICE Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Jaehoon Chung <jh80.chung@samsung.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
ce30e3ff |
|
31-Jan-2022 |
Simon Glass <sjg@chromium.org> |
scsi: Drop CONFIG_SYS_SCSI_MAX_DEVICE This is defined based on two other CONFIGs for all boards except sandbox and durian. For sandbox the value does not matter. For durian the value seems excessive. Drop the option completely, to simplify configuration and reduce the number of things we need to convert to Kconfig. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Stefan Roese <sr@denx.de>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
e6f6f9e6 |
|
10-May-2020 |
Simon Glass <sjg@chromium.org> |
common: Drop part.h from common header Move this uncommon header out of the common header. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
036218a6 |
|
11-Jan-2019 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Add the missing write operation support API_dev_write(va_list ap) is currently lacking the write support to storage devices because, historically, those devices did not implement block_write() The solution has been tested by loading and booting a (patched) GRUB instance in a QEMU vexpress-a9 environment. The disk write operations were triggered with GRUB's save_env command. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
8efae021 |
|
18-Dec-2018 |
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> |
api: storage: Fix enumeration of storage devices dev_stor_get() is not able to find the next available device in the current storage group when the previous enumerated device belongs to a different group or class (e.g. network). The root cause is the device group iterator not being reset after an unsuccessful search for the last returned device so that the following search for the next available device will start from beginning. The issue has been identified by loading and booting GRUB in a QEMU vexpress-a9 environment. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@iquestgroup.com>
|
#
83d290c5 |
|
06-May-2018 |
Tom Rini <trini@konsulko.com> |
SPDX: Convert all of our single license tags to Linux Kernel style When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us. In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style. This commit changes all instances where we have a single declared license in the tag as both the before and after are identical in tag contents. There's also a few places where I found we did not have a tag and have introduced one. Signed-off-by: Tom Rini <trini@konsulko.com>
|
#
10e40d54 |
|
14-Jun-2017 |
Simon Glass <sjg@chromium.org> |
Kconfig: Add CONFIG_SATA to enable SATA At present CONFIG_CMD_SATA enables the 'sata' command which also brings in SATA support. Some boards may wish to enable SATA without the command. Add a separate CONFIG to permit this. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
|
#
6d7a5707 |
|
20-Jun-2017 |
Emmanuel Vadot <manu@bidouilliste.com> |
api: Define a default mmc max device Define a default number of 1 for mmc max device if board config didn't specify one. Signed-off-by: Emmanuel Vadot <manu@bidouilliste.com> Reviewed-by: Simon Glass <sjg@chromium.org>
|
#
fc843a02 |
|
17-May-2017 |
Simon Glass <sjg@chromium.org> |
Kconfig: Add a CONFIG_IDE option At present IDE support is controlled by CONFIG_CMD_IDE. Add a separate CONFIG_IDE option so that IDE support can be enabled without requiring the 'ide' command. Update existing users and move the ide driver into drivers/block since it should not be in common/. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
f2288c5a |
|
07-Mar-2017 |
fuz@fuz.su <fuz@fuz.su> |
Apparent conflict between CONFIG_BLK and CONFIG_API Good evening, I am trying to port FreeBSD to the ASUS Tinker Board, a computer based on the Rockchip 3288 SoC. FreeBSD's boot loader (named loader(8)) needs CONFIG_API to be enabled, but trying to build an U-Boot from trunk with both CONFIG_API and CONFIG_BLK (as required for Rockchip SoC's?) leads to the following build failure: $ CROSS_COMPILE=arm-none-eabi- gmake tinker-rk3288_defconfig all ... CC api/api_storage.o api/api_storage.c: In function 'dev_read_stor': api/api_storage.c:334:9: error: 'struct blk_desc' has no member named 'block_read' if ((dd->block_read) == NULL) { ^~ api/api_storage.c:339:11: error: 'struct blk_desc' has no member named 'block_read' return dd->block_read(dd, start, len, buf); ^~ api/api_storage.c:340:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ gmake[2]: *** [scripts/Makefile.build:281: api/api_storage.o] Fehler 1 gmake[1]: *** [Makefile:1229: api] Fehler 2 gmake: *** [Makefile:460: __build_one_by_one] Error 2 I applied the following fix, but the product doesn't boot. Perhaps that's not a property of the fix though: Yours, Robert Clausecker
|
#
d3e8f630 |
|
04-Jan-2017 |
Emmanuel Vadot <manu@bidouilliste.com> |
api: storage: Test all block device in dev_stor_get In a config with one MMC at device id '1' and no MMC at device id '0' (a BeagleBone Black with no sd inserted for example), the current code will first test to access the MMC 0 (sd port), seeing that no device is present it will simply return that no more device are present for this class. This patch fixes this by testing all devices for each class. Signed-off-by: Emmanuel Vadot <manu@bidouilliste.com>
|
#
83f9ecbe |
|
22-Nov-2016 |
Walt Feasel <waltfeasel@gmail.com> |
Cosmetic api: api_storage.c Spelling correction Make spelling correction for 'from' Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
|
#
c9db75a0 |
|
22-Nov-2016 |
Walt Feasel <waltfeasel@gmail.com> |
Cosmetic api: api_storage.c Comment style Make comment style modifications Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
|
#
e3d7675a |
|
22-Nov-2016 |
Walt Feasel <waltfeasel@gmail.com> |
Cosmetic api: api_storage.c Line over 80 char Make checkpatch style modification for WARNING: line over 80 characters Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
|
#
b4c650d1 |
|
22-Nov-2016 |
Walt Feasel <waltfeasel@gmail.com> |
Cosmetic api: api_storage.c Blank line after { Make checkpatch style modification for CHECK: Blank lines aren't necessary after an open brace '{' Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
|
#
e5fbf2a7 |
|
22-Nov-2016 |
Walt Feasel <waltfeasel@gmail.com> |
Cosmetic api: api_storage.c Align parenthesis Make checkpatch style modification for CHECK: Alignment should match open parenthesis Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
|
#
5d81c6df |
|
19-Oct-2016 |
Emmanuel Vadot <manu@bidouilliste.com> |
api: storage: Avoid enumeration for non-configured subsystem If a subsystem wasn't configured, avoid enumeration. Signed-off-by: Emmanuel Vadot <manu@bidouilliste.com>
|
#
c649e3c9 |
|
01-May-2016 |
Simon Glass <sjg@chromium.org> |
dm: scsi: Rename CONFIG_CMD_SCSI to CONFIG_SCSI This option currently enables both the command and the SCSI functionality. Rename the existing option to CONFIG_SCSI since most of the code relates to the feature. Signed-off-by: Simon Glass <sjg@chromium.org>
|
#
db1d9e78 |
|
29-Feb-2016 |
Simon Glass <sjg@chromium.org> |
dm: blk: Rename get_dev() to blk_get_dev() The current name is too generic. Add a 'blk_' prefix to aid searching and make its purpose clearer. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> Tested-by: Stephen Warren <swarren@nvidia.com>
|
#
4101f687 |
|
29-Feb-2016 |
Simon Glass <sjg@chromium.org> |
dm: Drop the block_dev_desc_t typedef Use 'struct' instead of a typdef. Also since 'struct block_dev_desc' is long and causes 80-column violations, rename it to struct blk_desc. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> Tested-by: Stephen Warren <swarren@nvidia.com>
|
#
7c4213f6 |
|
07-Dec-2015 |
Stephen Warren <swarren@nvidia.com> |
block: pass block dev not num to read/write/erase() This will allow the implementation to make use of data in the block_dev structure beyond the base device number. This will be useful so that eMMC block devices can encompass the HW partition ID rather than treating this out-of-band. Equally, the existence of the priv field is crying out for this patch to exist. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Tom Rini <trini@konsulko.com>
|
#
ce2a07b7 |
|
13-Sep-2015 |
Andreas Färber <afaerber@suse.de> |
api_storage: Fix non-first storage device enumeration When enabling CONFIG_API and chain-loading GRUB2 on jetson-tk1, only the eMMC would show up as (hd0), but not the SD card, leading to GRUB not finding its configuration and modules, falling back to a rescue shell. This is because enum_ended would get set for !more after returning a cookie for the first MMC device in group 3. Fix this by properly setting the "more" argument also in the case of the first storage device of a group. Signed-off-by: Andreas Färber <afaerber@suse.de>
|
#
1a459660 |
|
08-Jul-2013 |
Wolfgang Denk <wd@denx.de> |
Add GPL-2.0+ SPDX-License-Identifier to source files Signed-off-by: Wolfgang Denk <wd@denx.de> [trini: Fixup common/cmd_io.c] Signed-off-by: Tom Rini <trini@ti.com>
|
#
84bf7ca5 |
|
13-May-2009 |
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> |
api: remove un-needed ifdef CONFIG_API already handle by the Makefile Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
|
#
6d0f6bcf |
|
16-Oct-2008 |
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> |
rename CFG_ macros to CONFIG_SYS Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
|
#
3d0ea311 |
|
24-Sep-2008 |
Matthias Fuchs <matthias.fuchs@esd-electronics.com> |
api: Fix building with CONFIG_API This patch fixes building with CONFIG_API and CONFIG_USB_STORAGE. USB_MAX_STOR_DEV is defined in include/usb.h, but needed in api/api_storage.c. Signed-off-by: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
|
#
f2302d44 |
|
06-Aug-2008 |
Stefan Roese <sr@denx.de> |
Fix merge problems Signed-off-by: Stefan Roese <sr@denx.de>
|
#
8d87589e |
|
28-Jul-2008 |
Rafal Jaworowski <raj@semihalf.com> |
API: Teach the storage layer about SATA and MMC options. Signed-off-by: Rafal Czubak <rcz@semihalf.com> Acked-by: Rafal Jaworowski <raj@semihalf.com>
|
#
13ca6305 |
|
28-Jul-2008 |
Rafal Jaworowski <raj@semihalf.com> |
API: Correct storage enumeration routine, other minor fixes in API storage area. Signed-off-by: Rafal Czubak <rcz@semihalf.com> Acked-by: Rafal Jaworowski <raj@semihalf.com>
|
#
1b769881 |
|
24-Jan-2008 |
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> |
Fix remaining CONFIG_COMMANDS update comments Fix coding style Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
|
#
500856eb |
|
09-Jan-2008 |
Rafal Jaworowski <raj@semihalf.com> |
API for external applications. This is an API for external (standalone) applications running on top of U-Boot, and is meant to be more extensible and robust than the existing jumptable mechanism. It is similar to UNIX syscall approach. See api/README for more details. Included is the demo application using this new framework (api_examples). Please note this is still an experimental feature, and is turned off by default. Signed-off-by: Rafal Jaworowski <raj@semihalf.com>
|