From: Felipe Balbi <me@felipebalbi.com>
To: suresh@mistralsolutions.com
Cc: linux-omap@vger.kernel.org
Subject: Re: Suggestion required to switch to a new kernel
Date: Thu, 3 Jul 2008 01:28:45 +0300 [thread overview]
Message-ID: <20080702222830.GD13834@frodo> (raw)
In-Reply-To: <20080702140237.qt1dx5beo70g8048@webmail.mistralsolutions.com>
On Wed, Jul 02, 2008 at 02:02:37PM -0500, suresh@mistralsolutions.com wrote:
> We are working on a product which is based on OMAP5912 (OSK). As of now,
> we are using linux-omap 2.6.16-rc3.
>
> We had issues with the JFFS2 cleanmarkers on oneNAND. JFFS2 driver in
> 2.6.16-rc3 did not understand the segmented OOB in oneNAND. Rather than
> trying to backport the driver fixes, we have decided to upgrade to a new
> kernel which includes that fix (We noticed that it was fixed in 2.6.21).
>
> We would really appreciate suggestions from people on the list about the
> kernel version that would be the best to switch to. We want to know which
> kernel version is stable on OMAP. Some of our requirements are;
>
> 1. DSP gateway should work on that kernel without any issues.
> 2. Power management should be functional. Our product uses power
> management to a great extent.
>
> We are thinking of 2.6.24 (or 2.6.23). Please let us know your suggestions.
Using current kernel versions is always a good idea. 2.6.24 should be
good for osk, but testing is always good.
Use the defconfig and change some options here and there and try it out.
Report here if you find any issues :-)
--
- Balbi
prev parent reply other threads:[~2008-07-02 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 19:02 Suggestion required to switch to a new kernel suresh
2008-07-02 22:28 ` Felipe Balbi [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=20080702222830.GD13834@frodo \
--to=me@felipebalbi.com \
--cc=linux-omap@vger.kernel.org \
--cc=suresh@mistralsolutions.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