ARM: Update mach-types
|ARM: Update mach-types | |This commit updates the mach-types based on the latest in Linus's head | |Signed-off-by: Marek Vasut <[email protected]>
Hi Marek,
Can I get you to do this again? I'd the symbol for MACH_MX6Q_SABRELITE.
Thanks
Troy
Quoted 11 lines
|ARM: Update mach-types | |This commit updates the mach-types based on the latest in Linus's head | |Signed-off-by: Marek Vasut <[email protected]>Hi Marek,
Can I get you to do this again? I'd the symbol for
MACH_MX6Q_SABRELITE.
No, can you please submit the mach-types update yourself? Thank you!
Quoted 6 lines · Marek Vasut
Quoted 6 lines
|ARM: Update mach-types | |This commit updates the mach-types based on the latest in Linus's head | |Signed-off-by: Marek Vasut<[email protected]>
Quoted 8 lines
Quoted 5 lines
Hi Marek,
Can I get you to do this again? I'd the symbol for
MACH_MX6Q_SABRELITE.No, can you please submit the mach-types update yourself? Thank you!
I don't think I'm trusted to do that. I think that some machines may have been removed
from Linux that u-boot may want to keep. Since I only want to use the value in 1 place,
is it acceptable to just use the hex value instead?
Thanks
Troy
Quoted 10 lines · Marek Vasut
Quoted 9 lines
Quoted 9 lines
|ARM: Update mach-types | |This commit updates the mach-types based on the latest in Linus'shead |
|Signed-off-by: Marek Vasut<[email protected]>Hi Marek,
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Can I get you to do this again? I'd the symbol for
MACH_MX6Q_SABRELITE.No, can you please submit the mach-types update yourself? Thank you!
I don't think I'm trusted to do that. I think that some machines may have been removed
from Linux that u-boot may want to keep.
So these machines have to define their mach id in their config (and you need to fix them after replacing mach-types).
Since I only want to use the
Quoted 2 lines
value in 1 place,
is it acceptable to just use the hex value instead?
No, either update the mach types (preffered) or ... Update the mach types ;)
Thanks in advance. M
Quoted 11 lines · Troy Kisky
|ARM: Update mach-types | |This commit updates the mach-types based on the latest in Linus's head | |Signed-off-by: Marek Vasut <[email protected]>Hi Marek,
Can I get you to do this again? I'd the symbol for
MACH_MX6Q_SABRELITE.
Just out of curiosity: Why do you need that?
It was my understanding that with recent U-Boot and Kernel on SabreLite DeviceTree is the way to go? And this doesn't need the mach-types any more?
Best regards
Dirk
Quoted 4 lines · Dirk Behme
Just out of curiosity: Why do you need that?
It was my understanding that with recent U-Boot and Kernel on SabreLite DeviceTree is the way to go? And this doesn't need the mach-types any more?
Maybe Troy wants to also allow U-boot to load a non-DT kernel, such as the one provided by Freescale?
Regards,
Fabio Estevam
Quoted 10 lines · Fabio Estevam
Quoted 4 lines · Dirk Behme
Just out of curiosity: Why do you need that?
It was my understanding that with recent U-Boot and Kernel on SabreLite DeviceTree is the way to go? And this doesn't need the mach-types any more?
Maybe Troy wants to also allow U-boot to load a non-DT kernel, such as the one provided by Freescale?
That's exactly right. With the addition of a couple of small things:
- machid
- revision tag (used by Freescale's kernel)
we can start shipping main-line U-Boot with Sabre Lite.
This seems like a worthwhile step, especially for those of us switching between kernels.
Am 28/02/2012 04:51, schrieb Marek Vasut:
Quoted 19 lines
Quoted 10 lines · Marek Vasut
Quoted 9 lines
Quoted 9 lines
|ARM: Update mach-types | |This commit updates the mach-types based on the latest in Linus'shead |
|Signed-off-by: Marek Vasut<[email protected]>Hi Marek,
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Can I get you to do this again? I'd the symbol for
MACH_MX6Q_SABRELITE.No, can you please submit the mach-types update yourself? Thank you!
I don't think I'm trusted to do that. I think that some machines may have been removed
from Linux that u-boot may want to keep.
Quoted 7 lines
So these machines have to define their mach id in their config (and you need to fix them after replacing mach-types).
Since I only want to use the
Quoted 2 lines
value in 1 place,
is it acceptable to just use the hex value instead?No, either update the mach types (preffered) or ... Update the mach types ;)
It was discussed and accepted that the boards can set CONFIG_MACH_TYPE directly into the configuration file. In this way, we continue to support in U-Boot boards independently if they are pushed to Linux mainline or not.
On the other side, everybody can send the current mach-types from the Linux kernel to Albert (ARM Maintainer) - if a board is already in kernel mainline is the preferred way.
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de =====================================================================
Quoted 29 lines · stefano babic
Am 28/02/2012 04:51, schrieb Marek Vasut:
Quoted 17 lines
Quoted 10 lines · Marek Vasut
Quoted 9 lines
Quoted 9 lines
|ARM: Update mach-types | |This commit updates the mach-types based on the latest in Linus'shead |
|Signed-off-by: Marek Vasut<[email protected]>Hi Marek,
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
Can I get you to do this again? I'd the symbol for
MACH_MX6Q_SABRELITE.No, can you please submit the mach-types update yourself? Thank you!
I don't think I'm trusted to do that. I think that some machines may have been removed
from Linux that u-boot may want to keep.Quoted 6 lines
So these machines have to define their mach id in their config (and you need to fix them after replacing mach-types).
Since I only want to use the
Quoted 2 lines
value in 1 place,
is it acceptable to just use the hex value instead?No, either update the mach types (preffered) or ... Update the mach types ;)
It was discussed and accepted that the boards can set
CONFIG_MACH_TYPEdirectly into the configuration file. In this way, we continue to support in U-Boot boards independently if they are pushed to Linux mainline or not.
Quoted 7 lines
On the other side, everybody can send the current mach-types from the Linux kernel to Albert (ARM Maintainer) - if a board is already in kernel mainline is the preferred way.
Best regards,
Stefano Babic
Thanks for the information. I'll send to Albert soon.
Troy