linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
Date: Wed, 26 Nov 2014 17:12:04 -0800	[thread overview]
Message-ID: <20141127011203.GR2817@atomide.com> (raw)
In-Reply-To: <201411270038.01312@pali>

* Pali Roh?r <pali.rohar@gmail.com> [141126 15:40]:
> 
> With enabled CONFIG_ARM_APPENDED_DTB=y file /proc/atags is 
> missing.

OK I guess it should not be needed for DT based booting.
 
> > The build_tag_list() should parse ATAG_REVISION and then
> > parse_tag_revision() should copy it to system_rev. Maybe try
> > adding some printks to see if those functions get called?
> 
> Now I see... Problem is that build_tag_list() is called from 
> convert_to_tag_list() which is called from setup_machine_tags() 
> which is called from setup_arch() only if setup_machine_fdt() 
> call fails. And it fails for *non* DT boot. You can check this 
> chain too.

Thinking about this probably the best long term solution is
to pass optional board_revision in the kernel cmdline that
can be parsed early and copied to system_rev variable.

Or if you can think of some other way to get it, we can set
system_rev in pdata-quirks.c.

Or maybe add some code to copy the ATAGs somewhere where
they are out of the way and don't conflict with the device
tree data? Then we can query ATAG_REVISION from pdata-quirks.c
and set system_rev.

Regards,

Tony

  reply	other threads:[~2014-11-27  1:12 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 20:00 [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode Tony Lindgren
2014-10-27 23:01 ` Aaro Koskinen
2014-10-28 22:12   ` Tony Lindgren
2014-10-29 13:43     ` Nishanth Menon
2014-10-29 18:59       ` Sebastian Reichel
2014-10-29 19:39         ` Tony Lindgren
2014-10-29 21:45           ` Nishanth Menon
2014-10-29 22:15             ` Tony Lindgren
2014-10-29 22:31             ` Aaro Koskinen
2014-10-30 13:55               ` Nishanth Menon
2014-10-29 23:07           ` Sebastian Reichel
2014-10-29 23:11           ` Aaro Koskinen
2014-10-29 23:54             ` Javier Martinez Canillas
2014-11-26 17:28   ` Pavel Machek
2014-11-26 18:19     ` Tony Lindgren
2014-11-26 18:57       ` Pali Rohár
2014-11-26 19:10         ` Tony Lindgren
2014-11-26 19:22           ` Pali Rohár
2014-11-26 20:08             ` Tony Lindgren
2014-11-26 23:01               ` Pali Rohár
2014-11-26 23:14                 ` Tony Lindgren
2014-11-26 23:38                   ` Pali Rohár
2014-11-27  1:12                     ` Tony Lindgren [this message]
2014-11-27 11:32                       ` Pali Rohár
2014-11-28 20:27                         ` Tony Lindgren
2014-11-28 21:41                           ` Pali Rohár
2014-11-28 22:24                             ` Tony Lindgren
2014-11-28 22:42                               ` Pali Rohár
2014-12-04 18:34                               ` Pali Rohár
2014-12-04 18:40                                 ` Tony Lindgren
2014-12-04 19:01                                   ` Pali Rohár
2014-11-28 22:26                             ` Aaro Koskinen
2014-11-28 22:43                               ` Pali Rohár
2014-11-28 22:41                             ` Aaro Koskinen
2014-11-28 22:49                               ` Pali Rohár
2014-11-28 22:54                                 ` Aaro Koskinen
2014-12-02 21:28                           ` Pali Rohár
2014-12-03 16:52                           ` Pavel Machek
2014-11-27 11:18               ` Pavel Machek
2014-10-31 19:30 ` Russell King - ARM Linux
2014-10-31 21:13   ` Tony Lindgren
2014-10-31 22:12     ` Tony Lindgren
2014-10-31 22:33     ` Russell King - ARM Linux
2014-10-31 23:37       ` Tony Lindgren
2014-11-01  0:44         ` Russell King - ARM Linux
2014-11-01 21:57           ` Tony Lindgren
2014-11-02 18:15             ` Tony Lindgren

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=20141127011203.GR2817@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).