From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips <linux-mips@linux-mips.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"Paoletti, Tomaso" <Tomaso.Paoletti@caviumnetworks.com>
Subject: Re: [PATCH 00/36] Add Cavium OCTEON processor support (v2).
Date: Wed, 29 Oct 2008 19:15:06 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.1.10.0810291905020.13373@ftp.linux-mips.org> (raw)
In-Reply-To: <490655B6.4030406@caviumnetworks.com>
On Mon, 27 Oct 2008, David Daney wrote:
> This patch set introduces preliminary support for Cavium Networks'
> OCTEON processor family. More information about these processors may
> be obtained here:
>
> http://www.caviumnetworks.com/OCTEON_MIPS64.html
Well, in the context of a technical mailing list there isn't much more
information available at the link you've quoted; although I do understand
you might not be the most appropriate person to point it to. Honestly,
stating: "The family comprises SOC devices built around MIPS64 cores"
would provide about as much (little) information as the web site does. :(
Maciej
next prev parent reply other threads:[~2008-10-29 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 23:58 [PATCH 00/36] Add Cavium OCTEON processor support (v2) David Daney
2008-10-28 0:04 ` [PATCH 30/36] Don't clobber spinlocks in 8250 David Daney
2008-10-28 0:04 ` [PATCH 31/36] Generic 8250 serial driver changes to support future OCTEON serial patches David Daney
2008-10-28 0:04 ` [PATCH 32/36] Allow port type to be specified when calling serial8250_register_port David Daney
2008-10-28 0:04 ` [PATCH 33/36] Allow port type to specify bugs that are not probed for David Daney
2008-10-28 0:04 ` [PATCH 34/36] 8250 serial driver changes for Cavium OCTEON David Daney
2008-10-29 19:15 ` Maciej W. Rozycki [this message]
2008-10-30 15:01 ` [PATCH 00/36] Add Cavium OCTEON processor support (v2) Chris Friesen
2008-11-04 14:48 ` Maciej W. Rozycki
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=alpine.LFD.1.10.0810291905020.13373@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=Tomaso.Paoletti@caviumnetworks.com \
--cc=akpm@linux-foundation.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@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