From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "Kevin Hilman" <khilman@deeprootsystems.com>,
"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: Fri, 5 Oct 2012 12:01:46 +0200 [thread overview]
Message-ID: <CAAwP0s2HTZNYP2qNkqnus9veh1qXH-V3gDU_qBBxRR6o2W+=OA@mail.gmail.com> (raw)
In-Reply-To: <20121005101009.7ed1fe85@skate>
On Fri, Oct 5, 2012 at 10:10 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
>
> On Fri, 5 Oct 2012 09:32:07 +0200, Javier Martinez Canillas wrote:
>
>> As Enric said, u-boot has SPL and NAND support for IGEP since
>> v2012.10-rc1. I just tried kernel a 3.6 with u-boot v2012.10-rc2 and
>> it works for me.
>
> Ok, I'll try this out.
>
>> But I agree that the kernel shouldn't do any assumptions about the
>> bootloader setting correctly the omap mux. Could you please share your
>> bootloader that makes the kernel to fail (or your IGEP NAND patches on
>> top of u-boot U-boot 2011.12) so I can reproduce the issue and try to
>> fix it?
>
> Ok, I'm using the X-Loader from git://git.igep.es/pub/scm/x-loader.git,
> tag v1.4.4-3, on top of which I apply
> http://git.free-electrons.com/training-materials/plain/lab-data/sysdev/u-boot/x-loader-1.4.4-3-igep-nand-support.patch
> to add support for the NAND-based IGEPv2 rev6.
>
> In terms of U-Boot, I use U-Boot 2011.12, on top of which I apply
> http://git.free-electrons.com/training-materials/plain/lab-data/sysdev/u-boot/u-boot-2011.12-igep-nand-support.patch
> to add support for the NAND-based IGEPv2 rev6.
>
> To make things easier if you don't need to rebuild those, I've put
> online pre-built binaries of X-Loader and U-Boot I'm using:
> http://free-electrons.com/~thomas/pub/igep-serial-problem/.
>
> Thanks,
>
> Thomas
Perfect, I'll try it and let you know if I find a fix for the issue.
Thanks a lot!
Javier
next prev parent reply other threads:[~2012-10-05 10:02 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
2012-10-05 7:32 ` Javier Martinez Canillas
2012-10-05 8:10 ` Thomas Petazzoni
2012-10-05 10:01 ` Javier Martinez Canillas [this message]
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='CAAwP0s2HTZNYP2qNkqnus9veh1qXH-V3gDU_qBBxRR6o2W+=OA@mail.gmail.com' \
--to=martinez.javier@gmail.com \
--cc=eballetbo@iseebcn.com \
--cc=gregory.clement@free-electrons.com \
--cc=khilman@deeprootsystems.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 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).