From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm mach-types.h
Date: Sun, 13 Nov 2011 00:58:42 +0100 [thread overview]
Message-ID: <201111130058.43026.michael@walle.cc> (raw)
Hi,
Does u-boot always follow the mach-types.h from upstream linux? Is there any
policy?
If thats true, it means, that
- every supported board in u-boot has to be supported in mainline linux,
too. because that is the basic requirement for an entry to stay in this
file.
- a device with device tree bindings, won't have any mach-type entry at all,
which means, that a distribution is not able to backport a device support
from DT form to an old-fashioned setup code (eg. support for a board on
older linux kernels, which doesn't have ARM device tree support).
IMHO u-boot should have its own mach-types.h (maybe autogenerated, like the
linux kernel do), just with entries for boards which are supported by u-boot.
This way, there won't be any problems with new board support patches.
Opinions?
--
Michael
next reply other threads:[~2011-11-12 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 23:58 Michael Walle [this message]
2011-11-13 0:32 ` [U-Boot] arm mach-types.h Marek Vasut
2011-11-13 10:10 ` Michael Walle
2011-11-13 16:18 ` Marek Vasut
2011-11-13 16:34 ` Michael Walle
2011-11-13 17:14 ` Marek Vasut
2011-11-13 17:52 ` Michael Walle
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=201111130058.43026.michael@walle.cc \
--to=michael@walle.cc \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.