From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm mach-types.h
Date: Sun, 13 Nov 2011 17:18:27 +0100 [thread overview]
Message-ID: <201111131718.27328.marek.vasut@gmail.com> (raw)
In-Reply-To: <201111131110.02331.michael@walle.cc>
> Am Sonntag 13 November 2011, 01:32:03 schrieb Marek Vasut:
> > > - 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.
> >
> > No, you can define CONFIG_MACH_TYPE MACH_TYPE_SOMETHING and
> > MACH_TYPE_SOMETHING nnn in your config file.
>
> well, according to this argumentation, there would be no need for
> mach-types.h at all. because if you rely on a mach-types.h definition and
> it is removed from linux, you have to switch to define it yourself anyway.
Not really, if you don't use it to boot linux, you don't need the mach id. Or if
you use dtree.
>
> > > 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.
> >
> > That would be insane due to colisions in the number assignment. See above
> > how to handle such trouble.
>
> of course with the same ids... (same source as the kernel mach-types, which
> is http://www.arm.linux.org.uk/developer/machines/download.php)
next prev parent reply other threads:[~2011-11-13 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 23:58 [U-Boot] arm mach-types.h Michael Walle
2011-11-13 0:32 ` Marek Vasut
2011-11-13 10:10 ` Michael Walle
2011-11-13 16:18 ` Marek Vasut [this message]
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=201111131718.27328.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--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