On Thu, Feb 04, 2021 at 12:02:52AM -0300, Fabio Estevam wrote:
Hi Tom,
On Wed, Feb 3, 2021 at 11:24 PM Tom Rini trini@konsulko.com wrote:
The i.MX8 family has never possibly supported ATAGs so we can remove
Yes, we don't need ATAGs for the i.MX family as we use devicetree for all i.MX members.
CONFIG_SERIAL_TAG support from that family. Furthermore, the i.MX7
but reading serial identification via fuses is still supported and I am not sure why this gets removed.
I am confused with this patch, as I don't understand the relationship between ATAG and CONFIG_SERIAL_TAG.
CONFIG_SERIAL_TAG is only used to configure the ATAG serial record. It does nothing else. On i.MX8* this is already being discarded. On i.MX7 we see things like: warp7 : all -144 rodata +32 text -176 u-boot: add: 0/-2, grow: 0/-2 bytes: 0/-160 (-160) function old new delta params 4 - -4 get_board_serial 20 - -20 board_late_init 96 56 -40 boot_prep_linux 156 60 -96
family is new enough to have never supported ATAGs so remove and disable those options as well.
Cc: Stefano Babic sbabic@denx.de Cc: Fabio Estevam festevam@gmail.com Cc: NXP i.MX U-Boot Team uboot-imx@nxp.com Signed-off-by: Tom Rini trini@konsulko.com
While I strongly suspect i.MX5 and older have board-file based Linux kernel support, I don't know where i.MX6 falls. Especially if you consider non-Linux OSes, so I didn't remove that. But I would like to know if we can also delete this code from there, or not. Thanks!
You can assume that all i.MX devices boot only via DT.
Currently, yes. Historically ever? Or even if so, you're OK just removing all of that code as well? Thanks.