public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: FEATURES prints
Date: Fri, 9 Oct 2009 09:15:08 -0500	[thread overview]
Message-ID: <4ACF456C.8080109@ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301DDD763EB@dbde02.ent.ti.com>

Premi, Sanjeev had written, on 10/09/2009 05:46 AM, the following:
>> -----Original Message-----
>> From: Menon, Nishanth 
>> Sent: Friday, October 09, 2009 12:43 AM
>> To: Premi, Sanjeev; linux-omap@vger.kernel.org
>> Subject: FEATURES prints
>>
>> Folks,
>>
>> With the addition of FEATURES in l-o, the following prints:
>>   - l2cache : Y
>>   - iva : Y
>>   - sgx : Y
>>   - neon : Y
>>   - isp : Y
>>
>> comes up on SDP3430 -> now that we will introduce half a 
>> dozen features 
> 
> [sp] The intention here is to print the features that help in
>      identifying the processor. Not really the board/EVM.
>      Even if there are more features, we decide which ones to
>      show.
this still a bunch of noise which is unusable for applications -> e.g. 
if an app wanted to use ISP, how would it do it?


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2009-10-09 14:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 19:13 FEATURES prints Nishanth Menon
2009-10-09 10:46 ` Premi, Sanjeev
2009-10-09 14:15   ` Nishanth Menon [this message]
2009-10-09 14:51     ` Premi, Sanjeev
2009-10-13 21:46 ` Kevin Hilman
2009-10-13 21:56   ` Premi, Sanjeev
2009-10-14  4:24     ` Shilimkar, Santosh
2009-10-14  4:48       ` Kevin Hilman
2009-11-12 21:02   ` Tony Lindgren
2009-11-12 23:36     ` Kevin Hilman

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=4ACF456C.8080109@ti.com \
    --to=nm@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@ti.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