From: "Kevin D. Kissell" <kevink@paralogos.com>
To: Anoop P A <an4linu@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: smtc support
Date: Fri, 12 Jun 2009 14:09:00 -0700 [thread overview]
Message-ID: <4A32C3EC.4060606@paralogos.com> (raw)
In-Reply-To: <eefc325c0906121335i6b575864kd10ca52948c36bd8@mail.gmail.com>
As the guy who wrote the SMTC stuff, I'd recommend picking up something
newer. Ralf has merged some of the subsequent improvements and fixes
into 2.6.18, but not the patches that I made last year to allow tickless
support, which is actually a very, very good thing to have for SMTC.
That support was initially available in 2.6.24, but subsequently got
broken by some changes to control register manipulation APIs that I
identified and fixed a few months ago. Ralf back-merged them into
several recent baselines, but I'm not sure which ones. 2.6.29-stable
seems to have all the right patches applied for SMTC, but of course I
can't tell whether there would be other issues for your platform.
Regards,
Kevin K.
Anoop P A wrote:
> Hi List,
>
> I have got a reference board with mips 34k core SOC.I am planning to
> enable smtc/smp support . The reference kernel I am having is
> linux-2.6.18 which is in uniprocessor mode.
>
> Could any of you suggest me in which way i have to proceed?. Does it
> make sense to continue using 2.6.18 or port newer kernel version (
> which might be having better SMTC/SMP support)?
>
> Thanks
> An
next prev parent reply other threads:[~2009-06-12 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 20:35 smtc support Anoop P A
2009-06-12 21:09 ` Kevin D. Kissell [this message]
2009-06-12 21:28 ` Anoop P A
2009-06-12 23:26 ` Kevin D. Kissell
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=4A32C3EC.4060606@paralogos.com \
--to=kevink@paralogos.com \
--cc=an4linu@gmail.com \
--cc=linux-mips@linux-mips.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 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.