Hello,
I am very newbie to core-boot and want to have my coreboot depict the fastboot functionality. Currently I am making the uboot load udc and fastboot function, to start the fastboot, without any involvement of coreboot. I want the udc and fastboot porting to coreboot.
I see some commit messages like "TEST=Compiles successfully. fastboot devices shows serial number for shark". Here, I understand that the udc driver is UP in coreboot and the fastboot command is invoked from host. But I am not sure how the command reaches to the udc drivers and then how it gives the data to the fastboot function.
AFAIU, fastboot is started at uboot with a cmd to uboot prompt. I am not sure how it will starts/ integrated/ works with coreboot. Is there any standard way?
Any light on this would be a great help.
It should be possible, to load fastboot directly as your coreboot payload.
On Wed, Mar 13, 2019 at 10:39 PM sriram.dash@samsung.com wrote:
Hello,
I am very newbie to core-boot and want to have my coreboot depict the fastboot functionality. Currently I am making the uboot load udc and fastboot function, to start the fastboot, without any involvement of coreboot. I want the udc and fastboot porting to coreboot.
I see some commit messages like "TEST=Compiles successfully. fastboot devices shows serial number for shark". Here, I understand that the udc driver is UP in coreboot and the fastboot command is invoked from host. But I am not sure how the command reaches to the udc drivers and then how it gives the data to the fastboot function.
AFAIU, fastboot is started at uboot with a cmd to uboot prompt. I am not sure how it will starts/ integrated/ works with coreboot. Is there any standard way?
Any light on this would be a great help. _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
The fastboot functionality mentioned there is most likely part of the depthcharge payload[0], which is based on the USB device mode drivers in libpayload[1]. fastboot in coreboot would mix up the responsibilities (coreboot: initialize hardware, payload: provide boot policy).
Patrick
[0] https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/refs/hea... [1] https://review.coreboot.org/cgit/coreboot.git/tree/payloads/libpayload/drive...
Am Do., 14. März 2019 um 06:39 Uhr schrieb sriram.dash@samsung.com:
Hello,
I am very newbie to core-boot and want to have my coreboot depict the fastboot functionality. Currently I am making the uboot load udc and fastboot function, to start the fastboot, without any involvement of coreboot. I want the udc and fastboot porting to coreboot.
I see some commit messages like "TEST=Compiles successfully. fastboot devices shows serial number for shark". Here, I understand that the udc driver is UP in coreboot and the fastboot command is invoked from host. But I am not sure how the command reaches to the udc drivers and then how it gives the data to the fastboot function.
AFAIU, fastboot is started at uboot with a cmd to uboot prompt. I am not sure how it will starts/ integrated/ works with coreboot. Is there any standard way?
Any light on this would be a great help. _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Hello Patrick,
Thanks for the heads up. I have checked the depthcharge payload and with add_gadget function call, it finds the udc and fastboot_proto_handler helps for functionality.
I will try to look in the similar direction. Thanks again for the direction.
Regards, Sriram --------- Original Message --------- Sender : Patrick Georgi via coreboot coreboot@coreboot.org Date : 2019-03-14 19:29 (GMT+5:30) Title : [coreboot] Re: Fastboot support for udc To : Sriram Dashsriram.dash@samsung.com CC : nullcoreboot@coreboot.org The fastboot functionality mentioned there is most likely part of the depthcharge payload[0], which is based on the USB device mode drivers in libpayload[1]. fastboot in coreboot would mix up the responsibilities (coreboot: initialize hardware, payload: provide boot policy). Patrick [0] https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/refs/hea... [1] https://review.coreboot.org/cgit/coreboot.git/tree/payloads/libpayload/drive... Am Do., 14. März 2019 um 06:39 Uhr schrieb sriram.dash@samsung.com:
Hello,
I am very newbie to core-boot and want to have my coreboot depict the fastboot functionality. Currently I am making the uboot load udc and fastboot function, to start the fastboot, without any involvement of coreboot. I want the udc and fastboot porting to coreboot.
I see some commit messages like "TEST=Compiles successfully. fastboot devices shows serial number for shark". Here, I understand that the udc driver is UP in coreboot and the fastboot command is invoked from host. But I am not sure how the command reaches to the udc drivers and then how it gives the data to the fastboot function.
AFAIU, fastboot is started at uboot with a cmd to uboot prompt. I am not sure how it will starts/ integrated/ works with coreboot. Is there any standard way?
Any light on this would be a great help. _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
-- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Paul Manicle, Halimah DeLaine Prado _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
-
Patrick Georgi -
ron minnich -
Sriram Dash -
sriram.dash＠samsung.com