From: "Pali Rohár" <pali.rohar@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Pavel Machek <pavel@ucw.cz>, Aaro Koskinen <aaro.koskinen@iki.fi>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
Date: Thu, 27 Nov 2014 12:32:47 +0100 [thread overview]
Message-ID: <201411271232.47231@pali> (raw)
In-Reply-To: <20141127011203.GR2817@atomide.com>
[-- Attachment #1: Type: Text/Plain, Size: 1829 bytes --]
On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
> * 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.
>
If I do not enable CONFIG_ARM_APPENDED_DTB=y then kernel is
booting in legacy mode (not in DT).
> > > 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.
>
Not possible. Our bootloader is closed & proprietary. I tried to
replace it with u-boot I was not able to do that. So we will use
that Nokia closed bootloader forever and it can provide data only
in ATAG structure.
> 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
If we are able to read ATAG from pdata-quirks, then we can parse
it there and fix problems... But I do not know if address of ATAG
structure is available there...
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: pali.rohar@gmail.com (Pali Rohár)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: Warn about deprecated legacy booting mode
Date: Thu, 27 Nov 2014 12:32:47 +0100 [thread overview]
Message-ID: <201411271232.47231@pali> (raw)
In-Reply-To: <20141127011203.GR2817@atomide.com>
On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
> * 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.
>
If I do not enable CONFIG_ARM_APPENDED_DTB=y then kernel is
booting in legacy mode (not in DT).
> > > 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.
>
Not possible. Our bootloader is closed & proprietary. I tried to
replace it with u-boot I was not able to do that. So we will use
that Nokia closed bootloader forever and it can provide data only
in ATAG structure.
> 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
If we are able to read ATAG from pdata-quirks, then we can parse
it there and fix problems... But I do not know if address of ATAG
structure is available there...
--
Pali Roh?r
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141127/04fc59bf/attachment-0001.sig>
next prev parent reply other threads:[~2014-11-27 11:32 UTC|newest]
Thread overview: 95+ 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 20:00 ` Tony Lindgren
2014-10-27 23:01 ` Aaro Koskinen
2014-10-27 23:01 ` Aaro Koskinen
2014-10-28 22:12 ` Tony Lindgren
2014-10-28 22:12 ` Tony Lindgren
2014-10-29 13:43 ` Nishanth Menon
2014-10-29 13:43 ` Nishanth Menon
2014-10-29 18:59 ` Sebastian Reichel
2014-10-29 18:59 ` Sebastian Reichel
2014-10-29 19:39 ` Tony Lindgren
2014-10-29 19:39 ` Tony Lindgren
2014-10-29 21:45 ` Nishanth Menon
2014-10-29 21:45 ` Nishanth Menon
2014-10-29 22:15 ` Tony Lindgren
2014-10-29 22:15 ` Tony Lindgren
2014-10-29 22:31 ` Aaro Koskinen
2014-10-29 22:31 ` Aaro Koskinen
2014-10-30 13:55 ` Nishanth Menon
2014-10-30 13:55 ` Nishanth Menon
2014-10-29 23:07 ` Sebastian Reichel
2014-10-29 23:07 ` Sebastian Reichel
2014-10-29 23:11 ` Aaro Koskinen
2014-10-29 23:11 ` Aaro Koskinen
2014-10-29 23:54 ` Javier Martinez Canillas
2014-10-29 23:54 ` Javier Martinez Canillas
2014-11-26 17:28 ` Pavel Machek
2014-11-26 17:28 ` Pavel Machek
2014-11-26 18:19 ` Tony Lindgren
2014-11-26 18:19 ` Tony Lindgren
2014-11-26 18:57 ` Pali Rohár
2014-11-26 18:57 ` Pali Rohár
2014-11-26 19:10 ` Tony Lindgren
2014-11-26 19:10 ` Tony Lindgren
2014-11-26 19:22 ` Pali Rohár
2014-11-26 19:22 ` Pali Rohár
2014-11-26 20:08 ` Tony Lindgren
2014-11-26 20:08 ` Tony Lindgren
2014-11-26 23:01 ` Pali Rohár
2014-11-26 23:01 ` Pali Rohár
2014-11-26 23:14 ` Tony Lindgren
2014-11-26 23:14 ` Tony Lindgren
2014-11-26 23:38 ` Pali Rohár
2014-11-26 23:38 ` Pali Rohár
2014-11-27 1:12 ` Tony Lindgren
2014-11-27 1:12 ` Tony Lindgren
2014-11-27 11:32 ` Pali Rohár [this message]
2014-11-27 11:32 ` Pali Rohár
2014-11-28 20:27 ` Tony Lindgren
2014-11-28 20:27 ` Tony Lindgren
2014-11-28 21:41 ` Pali Rohár
2014-11-28 21:41 ` Pali Rohár
2014-11-28 22:24 ` Tony Lindgren
2014-11-28 22:24 ` Tony Lindgren
2014-11-28 22:42 ` Pali Rohár
2014-11-28 22:42 ` Pali Rohár
2014-12-04 18:34 ` Pali Rohár
2014-12-04 18:34 ` Pali Rohár
2014-12-04 18:40 ` Tony Lindgren
2014-12-04 18:40 ` Tony Lindgren
2014-12-04 19:01 ` Pali Rohár
2014-12-04 19:01 ` Pali Rohár
2014-11-28 22:26 ` Aaro Koskinen
2014-11-28 22:26 ` Aaro Koskinen
2014-11-28 22:43 ` Pali Rohár
2014-11-28 22:43 ` Pali Rohár
2014-11-28 22:41 ` Aaro Koskinen
2014-11-28 22:41 ` Aaro Koskinen
2014-11-28 22:49 ` Pali Rohár
2014-11-28 22:49 ` Pali Rohár
2014-11-28 22:54 ` Aaro Koskinen
2014-11-28 22:54 ` Aaro Koskinen
2014-12-02 21:28 ` Pali Rohár
2014-12-02 21:28 ` Pali Rohár
2014-12-03 16:52 ` Pavel Machek
2014-12-03 16:52 ` Pavel Machek
2014-12-03 22:22 ` Dmitry Eremin-Solenikov
2014-11-27 11:18 ` Pavel Machek
2014-11-27 11:18 ` Pavel Machek
2014-10-31 19:30 ` Russell King - ARM Linux
2014-10-31 19:30 ` Russell King - ARM Linux
2014-10-31 21:13 ` Tony Lindgren
2014-10-31 21:13 ` Tony Lindgren
2014-10-31 22:12 ` Tony Lindgren
2014-10-31 22:12 ` Tony Lindgren
2014-10-31 22:33 ` Russell King - ARM Linux
2014-10-31 22:33 ` Russell King - ARM Linux
2014-10-31 23:37 ` Tony Lindgren
2014-10-31 23:37 ` Tony Lindgren
2014-11-01 0:44 ` Russell King - ARM Linux
2014-11-01 0:44 ` Russell King - ARM Linux
2014-11-01 21:57 ` Tony Lindgren
2014-11-01 21:57 ` Tony Lindgren
2014-11-02 18:15 ` 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=201411271232.47231@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tony@atomide.com \
/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.