From: Kevin Hilman <khilman@deeprootsystems.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "Enric Balletbò i Serra" <eballetbo@iseebcn.com>,
linux-omap@vger.kernel.org,
"Maxime Ripard" <maxime.ripard@free-electrons.com>,
"Gregory Clément" <gregory.clement@free-electrons.com>,
"Tony Lindgren" <tony@atomide.com>,
"Michael Opdenacker" <michael.opdenacker@free-electrons.com>
Subject: Re: ttyO2 broken on IGEPv2 on 3.3, 3.4-rc5 or arm-soc/for-next, working on 3.2
Date: Thu, 04 Oct 2012 16:08:19 -0700 [thread overview]
Message-ID: <87wqz5u97g.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20121004225704.0c08c862@skate> (Thomas Petazzoni's message of "Thu, 4 Oct 2012 22:57:04 +0200")
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> On Thu, 4 Oct 2012 22:30:58 +0200, Enric Balletbò i Serra wrote:
>
>> I recently tested kernel 3.6-rc5 and worked for me. Let me check tomorrow
>> kernel 3.6. Which u-boot version are you using?
>
> 2011.12 + a few patches to make the NAND of the IGEPv2 rev6 work. Let
> me try to build a recent U-Boot (which now includes the SPL for the
> IGEP) and see if it improves the situation.
>
> However, I believe that the rule is that the kernel shouldn't depend
> too much on initialization done by the bootloader, so it still seems
> like an issue to me.
Correct, if the kernel is relying on any bootloader assumptions, it
should be considered a kernel bug.
We'd really like to remove any bootloader assumptions from the kernel.
This will allow the kernel to be bootloader independent, and make it
easier to support reboot via kexec.
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-10-04 23:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 13:52 ttyO2 broken on IGEPv2 on 3.3, 3.4-rc5 or arm-soc/for-next, working on 3.2 Thomas Petazzoni
2012-05-04 16:27 ` Kevin Hilman
2012-05-04 17:51 ` Tony Lindgren
2012-05-04 23:46 ` Kevin Hilman
2012-10-04 16:07 ` Thomas Petazzoni
2012-10-04 17:18 ` Kevin Hilman
2012-10-04 20:11 ` Thomas Petazzoni
[not found] ` <CAKQ2WVp71=ULs_yK7Tkuo=8F4hATq0YCQ6RtV0ziJQQmnrib_g@mail.gmail.com>
2012-10-04 20:57 ` Thomas Petazzoni
2012-10-04 23:08 ` Kevin Hilman [this message]
2012-10-05 7:32 ` Javier Martinez Canillas
2012-10-05 8:10 ` Thomas Petazzoni
2012-10-05 10:01 ` Javier Martinez Canillas
2012-10-06 9:04 ` Enric Balletbò i Serra
2012-10-07 23:37 ` Javier Martinez Canillas
2012-10-04 23:06 ` Kevin Hilman
2012-10-05 8:06 ` Thomas Petazzoni
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=87wqz5u97g.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=eballetbo@iseebcn.com \
--cc=gregory.clement@free-electrons.com \
--cc=linux-omap@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=michael.opdenacker@free-electrons.com \
--cc=thomas.petazzoni@free-electrons.com \
--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.