From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Tim Sander <tim.sander@hbm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt7 - Error with low latency desktop config
Date: Thu, 11 Aug 2011 12:21:39 +0200 [thread overview]
Message-ID: <20110811102138.GC11398@pengutronix.de> (raw)
In-Reply-To: <201108101833.54661.tim.sander@hbm.com>
On Wed, Aug 10, 2011 at 06:33:54PM +0200, Tim Sander wrote:
> Hi Uwe
>
> I triple checked.
> > I think targetinstall should ask about the changed config items.
> It only asks one way, when going from an upatched kernel to an patched one.
> Since i was coming from an preempt rt kernel to an unpatched one no questions
> where asked (probably since all settings where still in place as i wasn't
> using the preempt rt feature with the preempt rt patched kernel source
> aka "Low latency desktop")
I guess that when the kernel build updates .config your
${PROJECT_DIR}/config/${PLATFORMNAME}/kernelconfig isn't adapted
accordingly. So yes, it might be out of sync. So better provide
${PROJECT_DIR}/${PLATFORMNAME}/build/linux-3.0/.config please.
> But i think the regression when going from 3.0-rt7 to 3.0.1-rt8 with
> CONFIG_PREEMPT_RTB is more worthwhile to discuss. Which i detailed in the
> other mail.
You didn't talk about CONFIG_PREEMPT_RTB before, did you? I just used it
as indicator that the .config you sent isn't for an -rt kernel.
Your machine is based on Phytec's pcm043? I could try to test on one of
those an unpatched -rt kernel, but I don't promise to come around to do it.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" 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:[~2011-08-11 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 13:53 [ANNOUNCE] 3.0-rt7 Peter Zijlstra
2011-08-05 9:12 ` hermann
2011-08-09 13:48 ` [ANNOUNCE] 3.0-rt7 - Error with low latency desktop config Tim Sander
2011-08-09 14:09 ` Uwe Kleine-König
2011-08-09 15:07 ` Tim Sander
2011-08-09 17:33 ` Uwe Kleine-König
2011-08-10 16:33 ` Tim Sander
2011-08-11 10:21 ` Uwe Kleine-König [this message]
2011-08-11 11:51 ` Tim Sander
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=20110811102138.GC11398@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tim.sander@hbm.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).