From: Matthew Wilcox <matthew@wil.cx>
To: linux-ia64@vger.kernel.org
Subject: Re: Montecito processor family
Date: Wed, 09 Nov 2005 15:24:47 +0000 [thread overview]
Message-ID: <20051109152447.GC27540@parisc-linux.org> (raw)
In-Reply-To: <42ADD890.1010406@free.fr>
On Wed, Nov 09, 2005 at 10:54:45PM +0900, Takayoshi Kochi wrote:
> I see that nothing has happend to Montecito's family name
> in both Linus' and Tony's tree since then.
>
> Is adding 'Itanium 2' for case 0x20 enough or do we need
> something different?
>
> Intel people may want to decide what it should be, according to
> their marketing/branding plan ;)
I'm sure they're having trouble getting that patch through Intel legal ;-)
Maybe we could put in a patch temporarily that calls it "Montecito",
then Intel can patch it to whatever the official marketing name is
upon release?
I'm not quite sure why we're so allergic to using the codenames in the
ia64 port. I mean, look at arch/i386/kernel/cpu/intel.c
next prev parent reply other threads:[~2005-11-09 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 19:03 Montecito processor family Menyhart, Zoltan
2005-06-13 19:17 ` Yu, Fenghua
2005-11-09 13:54 ` Takayoshi Kochi
2005-11-09 15:24 ` Matthew Wilcox [this message]
2005-11-10 1:50 ` Takayoshi Kochi
2006-06-01 0:03 ` Luck, Tony
2006-06-01 1:20 ` Matthew Wilcox
2006-06-01 3:06 ` Russ Anderson
2006-06-01 3:30 ` Alex Williamson
2006-06-01 16:32 ` Luck, Tony
2006-06-02 6:51 ` dann frazier
2006-06-02 22:18 ` Russ Anderson
2006-06-03 18:43 ` Luck, Tony
2006-06-03 19:23 ` David Mosberger-Tang
2006-06-05 20:37 ` Luck, Tony
2006-06-06 18:04 ` Chen, Kenneth W
2006-06-06 18:16 ` Alex Williamson
2006-06-06 18:59 ` Chen, Kenneth W
2006-06-07 9:22 ` Jes Sorensen
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=20051109152447.GC27540@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-ia64@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