From: Tony Lindgren <tony@atomide.com>
To: "Kridner, Jason" <jdk@ti.com>
Cc: "'k.kooi@student.utwente.nl'" <k.kooi@student.utwente.nl>,
"'linux-omap@vger.kernel.org'" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] Added support for OMAP35x processor series
Date: Wed, 6 Aug 2008 12:07:09 +0300 [thread overview]
Message-ID: <20080806090708.GH19813@atomide.com> (raw)
In-Reply-To: <8F7AF80515AF0D4D93307E594F3CB40E0AFDBE42@dlee03.ent.ti.com>
* Kridner, Jason <jdk@ti.com> [080805 17:12]:
> No, ROM CRC is useful for detecting between some device revisions, but not OMAp3430 vs OMAP3530.
>
> ----- Original Message -----
> From: Koen Kooi <k.kooi@student.utwente.nl>
> To: linux-omap@vger.kernel.org <linux-omap@vger.kernel.org>
> Cc: Kridner, Jason
> Sent: Tue Aug 05 05:10:40 2008
> Subject: Re: [PATCH] Added support for OMAP35x processor series
>
>
> Op 5 aug 2008, om 11:50 heeft Igor Stoppa het volgende geschreven:
>
> > On Tue, 2008-08-05 at 15:09 +0530, ext Premi, Sanjeev wrote:
> >> This patch is needed to ensure that we can make decisions based on
> >> the processor capabilities.
> >> E.g. OMAP3503 does not contain a DSP. We shouldn't be trying to
> >> disable/ manage the clocks for
> >> DSP on this processor. Same for SGX.
> >
> > Why can't the detection happen at runtime?
>
> AIUI the ID bits are the same (linux misdetect the 3530 on my beagle
> for a 3430). I heard that the only definitive way to do it at runtime
> is to CRC check the ROM code.
>
> Jason, is that correct?
Well if there's no way to detect certain omaps during runtime, please
patch arch/arm/plat-omap/common.c to have something like struct
omap_globals omap3503_globals.
BTW, why can't the dsp code detect if the DSP is there or not?
Tony
>
> regards,
>
> Koen
>
> >> Enabling NEON is support iby default is just based on the number of
> >> requests I have been getting
> >> from various users.
> >
> > Huh?
> >
> >
> > --
> >
> > Cheers, Igor
> >
> > ---
> >
> > Igor Stoppa
> > Maemo Software - Nokia Devices R&D - Helsinki
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-
> > omap" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
> N?????r??y????b?X??ǧv?^?){.n?+????{??f??{ay?\x1dʇڙ?,j\a??f???h???z?\x1e?w???\f???j:+v???w?j?m????\a????zZ+?????ݢj"??!
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" 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:[~2008-08-06 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 14:11 [PATCH] Added support for OMAP35x processor series Kridner, Jason
2008-08-06 9:07 ` Tony Lindgren [this message]
2008-08-06 9:46 ` Premi, Sanjeev
2008-08-06 10:10 ` Tony Lindgren
2008-08-06 11:56 ` Premi, Sanjeev
2008-08-08 7:39 ` Tony Lindgren
2008-09-01 19:56 ` [PATCH0/3] Add support for OMAP35x processors Premi, Sanjeev
[not found] <premi@ti.com>
2008-08-01 11:49 ` [PATCH] Added support for OMAP35x processor series Sanjeev Premi
2008-08-05 9:25 ` Tony Lindgren
2008-08-05 9:39 ` Premi, Sanjeev
2008-08-05 9:50 ` Igor Stoppa
2008-08-05 10:05 ` Premi, Sanjeev
2008-08-05 10:10 ` Koen Kooi
2008-08-05 10:13 ` Premi, Sanjeev
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=20080806090708.GH19813@atomide.com \
--to=tony@atomide.com \
--cc=jdk@ti.com \
--cc=k.kooi@student.utwente.nl \
--cc=linux-omap@vger.kernel.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