All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Eric B?nard <eric@eukrea.com>
Cc: meta-ti@yoctoproject.org, Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-devel@lists.openembedded.org,
	Thilo Fromm <fromm@dresearch-fe.de>
Subject: Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
Date: Mon, 21 May 2012 10:55:37 -0400	[thread overview]
Message-ID: <20120521145537.GA12334@denix.org> (raw)
In-Reply-To: <20120519102215.0b8edf4e@eb-e6520>

On Sat, May 19, 2012 at 10:22:15AM +0200, Eric B?nard wrote:
> Hi Denys,
> 
> Le Fri, 18 May 2012 17:48:33 -0400,
> Denys Dmytriyenko <denis@denix.org> a ?crit :
> > Netra and Centaurus are internal codenames for the SoC families behind those 
> > part numbers Koen mentioned above. Those codenames are not publicly advertised 
> > and Koen is just showing off after being on the inside... :) :-P
> > 
> these names were already dislosed on TI's website, for example :
> http://focus.ti.com/asia/download/1105-techday-abstracts-tw.pdf
> http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_Flashing_Tools_Guide
> 
> and are even in your slides where I first saw them ;-)
> https://wiki.yoctoproject.org/wiki/images/b/b3/Meta-ti.pdf

Good catch, but I didn't say they were secret :) I only said they were not 
advertised or marketed as official platform names. You can always find those 
references deep inside the code in several places...

So, it's understandable that customers may not know them, but it's fine to use 
those references among the developers.

-- 
Denys



WARNING: multiple messages have this Message-ID (diff)
From: Denys Dmytriyenko <denis@denix.org>
To: Eric B?nard <eric@eukrea.com>
Cc: meta-ti@yoctoproject.org, openembedded-devel@lists.openembedded.org
Subject: Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
Date: Mon, 21 May 2012 10:55:37 -0400	[thread overview]
Message-ID: <20120521145537.GA12334@denix.org> (raw)
In-Reply-To: <20120519102215.0b8edf4e@eb-e6520>

On Sat, May 19, 2012 at 10:22:15AM +0200, Eric B?nard wrote:
> Hi Denys,
> 
> Le Fri, 18 May 2012 17:48:33 -0400,
> Denys Dmytriyenko <denis@denix.org> a ?crit :
> > Netra and Centaurus are internal codenames for the SoC families behind those 
> > part numbers Koen mentioned above. Those codenames are not publicly advertised 
> > and Koen is just showing off after being on the inside... :) :-P
> > 
> these names were already dislosed on TI's website, for example :
> http://focus.ti.com/asia/download/1105-techday-abstracts-tw.pdf
> http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_Flashing_Tools_Guide
> 
> and are even in your slides where I first saw them ;-)
> https://wiki.yoctoproject.org/wiki/images/b/b3/Meta-ti.pdf

Good catch, but I didn't say they were secret :) I only said they were not 
advertised or marketed as official platform names. You can always find those 
references deep inside the code in several places...

So, it's understandable that customers may not know them, but it's fine to use 
those references among the developers.

-- 
Denys


  parent reply	other threads:[~2012-05-21 15:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 12:33 ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5 Thilo Fromm
2012-05-18 12:51 ` Koen Kooi
2012-05-18 12:51   ` Koen Kooi
2012-05-18 12:53   ` Thilo Fromm
2012-05-18 12:53     ` [oe] " Thilo Fromm
2012-05-18 12:55     ` [meta-ti] " Koen Kooi
2012-05-18 12:55       ` [oe] " Koen Kooi
2012-05-18 13:39       ` [meta-ti] " Thilo Fromm
2012-05-18 13:39         ` [oe] " Thilo Fromm
2012-05-18 13:52         ` [meta-ti] " Koen Kooi
2012-05-18 13:52           ` [oe] " Koen Kooi
2012-05-18 14:36           ` [meta-ti] " Monk, Roger
2012-05-18 14:36             ` [oe] " Monk, Roger
2012-05-18 14:55             ` [meta-ti] " Thilo Fromm
2012-05-18 14:55               ` [oe] " Thilo Fromm
2012-05-23  9:48               ` [meta-ti] " Steffen Sledz
2012-05-23  9:48                 ` [oe] " Steffen Sledz
2012-06-11 14:22                 ` [meta-ti] " Steffen Sledz
2012-06-11 14:22                   ` [oe] " Steffen Sledz
2012-06-19 14:43             ` [meta-ti] " Thilo Fromm
2012-06-19 14:43               ` [oe] " Thilo Fromm
2012-06-19 22:27               ` [meta-ti] " Monk, Roger
2012-06-19 22:27                 ` [oe] " Monk, Roger
2012-05-18 14:40           ` [meta-ti] " Thilo Fromm
2012-05-18 14:40             ` [oe] " Thilo Fromm
2012-05-18 14:47             ` [meta-ti] " Monk, Roger
2012-05-18 14:47               ` [oe] " Monk, Roger
2012-05-18 21:48             ` [meta-ti] " Denys Dmytriyenko
2012-05-18 21:48               ` [oe] " Denys Dmytriyenko
2012-05-19  8:22               ` [meta-ti] " Eric Bénard
2012-05-19  8:22                 ` [oe] " Eric Bénard
2012-05-21  8:00                 ` [meta-ti] " Thilo Fromm
2012-05-21  8:00                   ` [oe] " Thilo Fromm
2012-05-21 14:55                 ` Denys Dmytriyenko [this message]
2012-05-21 14:55                   ` Denys Dmytriyenko

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=20120521145537.GA12334@denix.org \
    --to=denis@denix.org \
    --cc=eric@eukrea.com \
    --cc=fromm@dresearch-fe.de \
    --cc=koen@dominion.thruhere.net \
    --cc=meta-ti@yoctoproject.org \
    --cc=openembedded-devel@lists.openembedded.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.