From: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linux-mips@linux-mips.org, Jonas Gorski <jogo@openwrt.org>,
Mathias Kresin <openwrt@kresin.me>
Subject: Re: [RFC PATCH] Re: Adding support for device tree and command line
Date: Thu, 26 May 2016 10:24:55 -0700 [thread overview]
Message-ID: <1464283495.5020.16.camel@chimera> (raw)
In-Reply-To: <57472386.8030605@hauke-m.de>
On Thu, 2016-05-26 at 18:25 +0200, Hauke Mehrtens wrote:
> I like it in the ARM arch code that the SoC specific code does not
> have
> to take care of this stuff. The normal arch code provides the device
> tree and so on.
Well, MIPS bootloaders are strikingly more diverse than on ARM…
> Can we at least add a function to mips which will read the device tree
> and the kernel cmd, so I do not have to open code it for each SoC, but
> only call this function.
That would take a serious arch overhaul not unlike the migration to DT,
and I suspect multiple targets would break. So far, this argc == -2
stuff has been used on only two targets that I could see, so I don't
believe it belongs in head.S even with such an overhaul. That said, if
_real_ UHI spec compliance gets in, the SoC-specific stuff could just be
dropped. In the meantime, I propose this patch with the changes
previously suggested.
next prev parent reply other threads:[~2016-05-26 17:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 21:14 Adding support for device tree and command line Hauke Mehrtens
2016-05-23 21:34 ` Hauke Mehrtens
2016-05-23 22:12 ` Daniel Gimpelevich
2016-05-24 5:32 ` [RFC PATCH] " Daniel Gimpelevich
2016-05-24 11:27 ` Antony Pavlov
2016-05-24 15:15 ` Daniel Gimpelevich
2016-05-24 15:27 ` Daniel Gimpelevich
2016-05-24 16:48 ` Antony Pavlov
2016-05-24 17:00 ` Daniel Gimpelevich
2016-05-25 3:31 ` Antony Pavlov
2016-05-25 3:33 ` Daniel Gimpelevich
2016-05-27 21:06 ` [PATCH v2] " Daniel Gimpelevich
2016-05-28 10:31 ` Antony Pavlov
2016-05-28 19:05 ` Daniel Gimpelevich
2016-05-29 1:23 ` Daniel Gimpelevich
2016-05-30 17:24 ` Antony Pavlov
2016-05-29 10:53 ` Jonas Gorski
2016-05-29 18:38 ` Daniel Gimpelevich
2016-05-29 19:01 ` Jonas Gorski
2016-05-29 19:08 ` Daniel Gimpelevich
2016-05-29 19:22 ` Jonas Gorski
2016-05-29 19:26 ` Daniel Gimpelevich
2016-05-29 19:30 ` Jonas Gorski
2016-05-29 21:19 ` Daniel Gimpelevich
2016-05-26 16:25 ` [RFC PATCH] " Hauke Mehrtens
2016-05-26 17:24 ` Daniel Gimpelevich [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-24 5:19 Daniel Gimpelevich
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=1464283495.5020.16.camel@chimera \
--to=daniel@gimpelevich.san-francisco.ca.us \
--cc=hauke@hauke-m.de \
--cc=jogo@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=openwrt@kresin.me \
/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