From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] RFC: arm: add call to cleanup things before jumping into kernel
Date: Thu, 3 Oct 2013 17:44:28 +0200 [thread overview]
Message-ID: <20131003174428.6fd681f0@lilith> (raw)
In-Reply-To: <CAEC9eQOsUr-2AMUGnoXy5-EOAYLsxYySHWxTdfhq_biD_mzNXA@mail.gmail.com>
Hi Ajay,
On Thu, 3 Oct 2013 14:49:49 +0530, Ajay kumar <ajaynumb@gmail.com>
wrote:
> Hi Albert,
>
>
> On Thu, Oct 3, 2013 at 2:28 PM, Albert ARIBAUD <albert.u.boot@aribaud.net>wrote:
>
> > Hi Ajay,
> >
> > On Thu, 03 Oct 2013 14:34:19 +0530, Ajay Kumar
> > <ajaykumar.rs@samsung.com> wrote:
> >
> > > Add infrasturcture to cleanup any of those architecture related settings
> > > done for u-boot, if they can cause problem during kernel boot.
> > >
> > > Signed-off-by: Ajay Kumar <ajaykumar.rs@samsung.com>
> > > ---
> >
> > Regardless to ma question re fixing the issue in U-Boot or Linux: does
> > something prevent using the already existing cleanup_before_linux()
> > function, and if not, what made you choose to create another one
> > instead?
> >
(fixed quote glitch here that put the start of your reply inside mine.)
> cleanup_before_linux() generally cleans up things specific to the
> processor.
> I thought of introducing a cleanup function which would allow us to cleanup
> things which are SOC specific(all SOC under armv7 as per the patch).
> And, used the same function to cleanup some exynos specific stuff before
> booting linux.
> May be, I should have used a different name instead of
> arch_cleanup_before_linux?
Well, if it is *SoC* specific, then it is not *arch* specific, so yes,
the name should be changed. Now, we don't really have a concept of
'SoC-specific' in U-Boot, so board-specific, as suggested by Simon, is
the 'next not-too-worst thing'.
Still, don't rush to provide a new patch. According to Simon, the Linux
panic was solved and might just not have hit mainline yet; if that is
confirmed, then renaming arch_cleanup_before_linux() becomes moot.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-10-03 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 9:04 [U-Boot] [PATCH 1/2] RFC: arm: add call to cleanup things before jumping into kernel Ajay Kumar
2013-10-03 8:58 ` Albert ARIBAUD
2013-10-03 9:19 ` Ajay kumar
2013-10-03 15:44 ` Albert ARIBAUD [this message]
2013-10-04 5:56 ` Ajay kumar
2013-10-03 14:23 ` Simon Glass
2013-10-03 9:04 ` [U-Boot] [PATCH 2/2] RFC: exynos: Disable the display controller when starting Linux Ajay Kumar
2013-10-03 8:55 ` Albert ARIBAUD
2013-10-03 9:24 ` Ajay kumar
2013-10-03 14:21 ` Simon Glass
2013-10-04 5:52 ` Ajay kumar
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=20131003174428.6fd681f0@lilith \
--to=albert.u.boot@aribaud.net \
--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