From: mailander <mailander@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels
Date: Sat, 03 Mar 2012 11:43:11 +0100 [thread overview]
Message-ID: <4F51F5BF.1040601@gmx.de> (raw)
In-Reply-To: <20120303093826.C3054126F3B0@gemini.denx.de>
On 03/03/2012 10:38, Wolfgang Denk wrote:
> Dear Dirk,
>
> In message <4F51BBA9.4090608@googlemail.com> you wrote:
>>
>> Having Freescale working on these quite old and unclean U-Boot and
>> Kernel versions is a pain. Kernel is an other topic, but with U-Boot,
>> thanks to the very good work of everybody, we are in a good position
>> to get rid of the old Freescale U-Boot, now. And get everybody to work
>> with mainline and create patches against it.
>
> ACK.
>
>> So if it helps to apply some backward compatibility to make it easier
>> for everybody, esp. Freescale, to switch to mainline U-Boot, I think
>> we should try it.
>
> Agreed. If these patches were only for backward compatibility I would
> not complain much. But they are known to introduce forward incompati-
> bilities with all this MACH_ID stuff, and this is what I would like to
> avoid.
>
> I think we should make a clear statement that new boards that get
> added should only support DT based configurations. If really needed,
> legacy MACH_ID support may be kept out of tree.
I think a point here is that boards must not use any macro defined in
mach-types.h, such as machine_is_*. U-Boot does not need it, and their
usage makes the code strictly dependent from the kernel legacy mach-ids.
If a board defines only CONFIG_MACH_TYPE in its own configuration file,
it should not break if we decide in future to drop it completely.
Best regards,
Stefano Babic
next prev parent reply other threads:[~2012-03-03 10:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 22:55 [U-Boot] i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels Eric Nelson
2012-03-02 22:55 ` [U-Boot] [PATCH 1/3] i.MX6: mx6qsabrelite: add CONFIG_REVISION_TAG Eric Nelson
2012-03-02 22:59 ` Marek Vasut
2012-03-04 20:35 ` Eric Nelson
2012-03-04 20:59 ` Marek Vasut
2012-03-04 21:04 ` Eric Nelson
2012-03-04 21:18 ` Marek Vasut
2012-03-04 22:06 ` Wolfgang Denk
2012-03-04 22:41 ` Eric Nelson
2012-03-03 10:26 ` Stefano Babic
2012-03-02 22:55 ` [U-Boot] [PATCH 2/3] i.MX6: mx6qsabrelite: add MACH_TYPE_MX6Q_SABRELITE Eric Nelson
2012-03-02 23:00 ` Marek Vasut
2012-03-03 10:28 ` Stefano Babic
2012-03-02 22:55 ` [U-Boot] [PATCH 3/3] i.MX6: mx6qsabrelite: add ext2 support Eric Nelson
2012-03-07 9:36 ` Stefano Babic
2012-03-02 23:01 ` [U-Boot] i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels Marek Vasut
2012-03-02 23:25 ` Wolfgang Denk
2012-03-02 23:46 ` Eric Nelson
2012-03-02 23:50 ` Fabio Estevam
2012-03-03 9:33 ` Wolfgang Denk
2012-03-03 6:35 ` Dirk Behme
2012-03-03 9:38 ` Wolfgang Denk
2012-03-03 10:43 ` mailander [this message]
2012-03-03 11:32 ` Dirk Behme
2012-03-03 13:30 ` Wolfgang Denk
2012-03-04 1:19 ` Troy Kisky
2012-03-04 8:39 ` Wolfgang Denk
2012-03-07 9:37 ` Albert ARIBAUD
2012-03-04 11:09 ` Stefano Babic
2012-03-04 14:14 ` Igor Grinberg
2012-03-04 19:45 ` [U-Boot] CONFIG_REVISION (was i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels) Eric Nelson
2012-03-07 8:43 ` Stefano Babic
2012-03-07 15:53 ` Eric Nelson
2012-03-07 16:32 ` Stefano Babic
2012-03-03 10:33 ` [U-Boot] i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels Stefano Babic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F51F5BF.1040601@gmx.de \
--to=mailander@gmx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox