public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] yet another arm mach-types.h thread
Date: Thu, 24 Nov 2011 23:29:40 +0100	[thread overview]
Message-ID: <201111242329.40991.michael@walle.cc> (raw)


Hi,

As there was no real conclusion on my previous "arm mach-types.h" thread, i 
have to reemphasize that the current mach types handling is broken.

 1. u-boot follows linux mach-types.h
 2. linux only includes ids
     a, they have (non DT!) board support for or
     b, id which are not older than 12 months.

Now there are the following cases with problems:
 - boards which have no linux support but uboot support
 - boards which have only dt support within linux. uboot won't be able to boot
   these board with older kernels, which do not have dt support, but instead
   still using the old-fashioned setup code.
 - boards which have only dt support in mainline kernel but have been
   backported to older kernels and old-fashioned setup code.
 - there will always be regressions when pulling the newest mach-types.h from
   linux

The proposed solution was to add the ID to the board config. Why not put all 
ids into the board configs then and remove the mach-types.h? Maybe you want to 
have database with all ids? But with tracking the linux mach-types.h you 
always have the database with boards _linux mainline_ supports and not the 
boards uboot supports. Something seems to be broken there :)

IMHO either you say
 - you have a database, that way you have to include the ids _you_ support or
 - you don't have such a file and have the ids scattered all across the board
   configs.
 
-- 
Michael

             reply	other threads:[~2011-11-24 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 22:29 Michael Walle [this message]
2011-11-25 19:33 ` [U-Boot] yet another arm mach-types.h thread Albert ARIBAUD

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=201111242329.40991.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox