From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] board/BuR/zynq/brsmarc2: initial commit
Date: Fri, 3 May 2019 13:35:11 -0400 [thread overview]
Message-ID: <20190503173511.GX31207@bill-the-cat> (raw)
In-Reply-To: <22d7e2f5-148a-59de-f45e-3fec5787e13d@xilinx.com>
On Fri, May 03, 2019 at 09:29:32AM -0700, Michal Simek wrote:
[snip]
> I think we need to get more clarity what exactly vxworks expects and
> what are just your "hacks" to get it work.
> If vxworks deviates existing dt binding, or create completely new one.
Hold up. If it's not in the spec itself (and most stuff is not), the
Linux bindings are no more authoritative than the BSD ones (which are
also not, unless things have changed, the Linux ones) than the vxWorks
ones than anything else. For a board that is not supported in Linux, I
don't think it makes sense to treat the primary OS support as something
that's added to another DT.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190503/ac0bbb87/attachment.sig>
next prev parent reply other threads:[~2019-05-03 17:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 12:14 [U-Boot] [PATCH v2] board/BuR/zynq/brsmarc2: initial commit Hannes Schmelzer
2019-05-02 16:06 ` Michal Simek
2019-05-02 18:34 ` Hannes Schmelzer
2019-05-02 19:03 ` Tom Rini
2019-05-03 11:17 ` Hannes Schmelzer
2019-05-03 11:34 ` Hannes Schmelzer
2019-05-03 13:18 ` Tom Rini
2019-05-03 16:29 ` Michal Simek
2019-05-03 17:35 ` Tom Rini [this message]
2019-05-03 17:36 ` Tom Rini
2019-05-03 17:49 ` Michal Simek
2019-05-03 18:04 ` Tom Rini
2019-05-03 18:15 ` Michal Simek
2019-05-08 12:37 ` Hannes Schmelzer
2019-05-09 21:49 ` Michal Simek
2019-05-10 5:49 ` Hannes Schmelzer
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=20190503173511.GX31207@bill-the-cat \
--to=trini@konsulko.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 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.