From: Ladislav Michl <ladis@linux-mips.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] igep00x0: consolidate defconfigs
Date: Wed, 21 Sep 2016 11:39:19 +0200 [thread overview]
Message-ID: <20160921093919.GA945@localhost.localdomain> (raw)
In-Reply-To: <20160921002636.GB29602@bill-the-cat>
On Tue, Sep 20, 2016 at 08:26:36PM -0400, Tom Rini wrote:
> On Wed, Sep 21, 2016 at 01:52:21AM +0200, Ladislav Michl wrote:
> > On Tue, Sep 20, 2016 at 07:45:14PM -0400, Tom Rini wrote:
[snip]
> > > But why do we even need to set MACH_TYPE these days?
> >
> > That's only needed for non-device tree kernel boot. These boards run mostly
> > vendor provided kernels based on TI 2.6.32 or 2.6.37 kernel tree with
> > daughter boards specific patches on top of it. Enric is concerned not
> > to break that support, so I'm trying to keep it.
>
> OK, if you're still supporting stuff that old then yes, it makes sense.
> And we can't get this right at run time?
I asked several times, if there's a way to differentiate those boards
(0020, 0030 and 0032) at runtime, but never get an answer. Of course
I'd like to see one U-Boot binary to rule them all, but I'm out of clue
there. Few people added to Cc...
Another approach might be to configure U-Boot using FDT and translate
that information into MACH_TYPE and kernel command line to support
non-device tree enabled kernels.
ladis
next prev parent reply other threads:[~2016-09-21 9:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 9:04 [U-Boot] [PATCH 1/3] igep00x0: disable CONFIG_DISPLAY_BOARDINFO Ladislav Michl
2016-09-20 9:07 ` [U-Boot] [PATCH 2/3] igep00x0: consolidate defconfigs Ladislav Michl
2016-09-20 12:52 ` Tom Rini
2016-09-20 22:44 ` Ladislav Michl
2016-09-20 23:45 ` Tom Rini
2016-09-20 23:52 ` Ladislav Michl
2016-09-21 0:26 ` Tom Rini
2016-09-21 9:39 ` Ladislav Michl [this message]
2016-09-21 11:46 ` Enric Balletbo Serra
2016-09-21 12:51 ` Tom Rini
2016-09-21 13:46 ` Enric Balletbo Serra
2016-09-21 14:02 ` Tom Rini
2016-09-22 5:12 ` Ladislav Michl
2016-09-20 9:09 ` [U-Boot] [PATCH 3/3] igep00x0: add Hynix timings Ladislav Michl
2016-09-20 15:41 ` [U-Boot] [PATCH 1/3] igep00x0: disable CONFIG_DISPLAY_BOARDINFO Enric Balletbo Serra
2016-09-20 23:10 ` Ladislav Michl
2016-11-04 11:47 ` Ladislav Michl
2016-11-04 11:55 ` [U-Boot] [PATCHv2 " Ladislav Michl
[not found] ` <ef3936d3-3967-bc71-4fdc-7a78b12a3c45@osg.samsung.com>
2016-11-04 17:21 ` Ladislav Michl
2016-11-04 19:34 ` Javier Martinez Canillas
2016-11-04 19:36 ` Javier Martinez Canillas
2016-11-13 20:58 ` [U-Boot] [U-Boot, PATCHv2, " Tom Rini
2016-11-04 11:57 ` [U-Boot] [PATCHv2 2/3] igep00x0: consolidate defconfigs Ladislav Michl
2016-11-04 19:37 ` Javier Martinez Canillas
2016-11-13 20:58 ` [U-Boot] [U-Boot,PATCHv2,2/3] " Tom Rini
2016-11-04 11:59 ` [U-Boot] [PATCHv2 3/3] igep00x0: add Hynix timings Ladislav Michl
2016-11-04 19:39 ` Javier Martinez Canillas
2016-11-13 20:58 ` [U-Boot] [U-Boot,PATCHv2,3/3] " Tom Rini
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=20160921093919.GA945@localhost.localdomain \
--to=ladis@linux-mips.org \
--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.