From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sre@debian.org>
Cc: linux-omap@vger.kernel.org
Subject: Re: HSI: any status updates on omap_ssi?
Date: Tue, 24 Apr 2012 09:42:55 -0700 [thread overview]
Message-ID: <20120424164255.GO3739@atomide.com> (raw)
In-Reply-To: <20120424162754.GA9407@earth.universe>
* Sebastian Reichel <sre@debian.org> [120424 09:31]:
> On Tue, Apr 24, 2012 at 08:23:16AM -0700, Tony Lindgren wrote:
> > * Sebastian Reichel <sre@debian.org> [120421 04:26]:
> > > Hi,
> > >
> > > Missing omap_ssi support is currently the most important missing
> > > feature, to make the mainline kernel on the Nokia N900 useful, see
> > > also [0].
> > >
> > > Can you prepare SSI inclusion into the mainline kernel, now that HSI
> > > has been pulled into 3.4? Do you think we get SSI support in 3.5?
> >
> > Also FYI related to n900, you need to have bce492c0 (ARM: OMAP2+: UART: Fix
> > incorrect population of default uart pads) applied after v3.1 if using
> > CONFIG_OMAP_MUX to avoid some SSI pins getting wronly muxed to UART.
>
> Thanks for the info.
>
> > Then to verify, the hw floating point error you reported a while back
> > with omap2plus_defconfig got resolved, right?
>
> I have not tried again since then. The error only occured, if the
> kernel has been built with OMAP2 support. It does not show up on
> kernels, which support only OMAP3/OMAP4.
I believe last time I checked it few weeks back it worked correctly with
omap2 compiled in. Or else there are some other .config options needed too.
Care to verify that?
Regards,
Tony
prev parent reply other threads:[~2012-04-24 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 10:52 HSI: any status updates on omap_ssi? Sebastian Reichel
2012-04-24 15:23 ` Tony Lindgren
2012-04-24 16:27 ` Sebastian Reichel
2012-04-24 16:42 ` Tony Lindgren [this message]
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=20120424164255.GO3739@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=sre@debian.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