From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] nitrogen6x: Pass the correct CPU revision to the kernel
Date: Sat, 16 Mar 2013 21:14:59 +0100 [thread overview]
Message-ID: <20130316201459.7888C200301@gemini.denx.de> (raw)
In-Reply-To: <51449A34.7080902@boundarydevices.com>
Dear Eric Nelson,
In message <51449A34.7080902@boundarydevices.com> you wrote:
>
> At the moment, it doesn't.
>
> I would really like to see us (the i.MX6 community) standardize
> the use of some fuses to specifically mean board revision.
No. This is a very bad idea. We've been working long enough with a
number of board manufacturers; many of these provides SOMs (Systems on
Module) that get then used by many different customers for many
different purposes - and the use of things like fuse settings should
be left to these end users.
> We're contemplating some board changes such as switching the
> ethernet PHY and having a convention for the use of a few
> bits in OTP would allow us to implement get_board_rev() once in
> a common place.
>
> Over the lifetime of most boards, it's likely that at least
> one board revision will have software implications and having
> a common way to express/detect this could prevent some churn
> in board-specific files.
>
> Such a convention would need to have broad sign off though.
You seem to forget that there is a standardized, well documented way
to pass all kind of hardware related information to the Linux kernel.
If you need any such information, add it to the device tree.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If you're not part of the solution, you're part of the problem.
next prev parent reply other threads:[~2013-03-16 20:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 21:06 [U-Boot] [PATCH 1/2] nitrogen6x: Pass the correct CPU revision to the kernel Fabio Estevam
2013-03-15 21:06 ` [U-Boot] [PATCH 2/2] mx6qsabrelite: Do not hardcode the CPU revision Fabio Estevam
2013-03-16 5:59 ` Dirk Behme
2013-03-16 8:19 ` Wolfgang Denk
2013-03-16 14:50 ` Fabio Estevam
2013-03-16 14:52 ` Otavio Salvador
2013-03-16 15:01 ` Fabio Estevam
2013-03-16 16:32 ` Otavio Salvador
2013-03-16 19:41 ` Fabio Estevam
2013-03-16 0:20 ` [U-Boot] [PATCH 1/2] nitrogen6x: Pass the correct CPU revision to the kernel Eric Nelson
2013-03-16 14:58 ` Fabio Estevam
2013-03-16 16:13 ` Eric Nelson
2013-03-16 16:55 ` Dirk Behme
2013-03-16 20:17 ` Wolfgang Denk
2013-03-16 19:48 ` Fabio Estevam
2013-03-16 20:27 ` Eric Nelson
2013-03-25 19:14 ` Eric Nelson
2013-03-26 2:25 ` Fabio Estevam
2013-03-26 3:27 ` Fabio Estevam
2013-03-16 20:29 ` Wolfgang Denk
2013-03-16 20:14 ` Wolfgang Denk [this message]
2013-03-26 15:24 ` Eric Nelson
2013-03-26 15:26 ` Eric Nelson
2013-03-26 18:06 ` Fabio Estevam
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=20130316201459.7888C200301@gemini.denx.de \
--to=wd@denx.de \
--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