linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Chou <thomas@wytron.com.tw>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Baruch Siach <baruch@tkos.co.il>,
	Andrew Morton <akpm@linux-foundation.org>,
	Indan Zupancic <indan@nul.nu>, Greg KH <greg@kroah.com>,
	Alex Gershgorin <agersh@rambler.ru>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>, Jiri Slaby <jslaby@suse.cz>,
	Nios2 development list <nios2-dev@sopc.et.ntust.edu.tw>
Subject: Re: [PATCHv3] drivers/misc: Altera active serial implementation
Date: Thu, 18 Nov 2010 10:15:10 +0800	[thread overview]
Message-ID: <4CE48C2E.5080502@wytron.com.tw> (raw)
In-Reply-To: <4CE42457.8090001@zytor.com>

Hi hpa,

On 11/18/2010 02:52 AM, H. Peter Anvin wrote:
> Do you happen to have a sample STmicro part number?  Also, are you
> saying that EPCS is *only* serial flash, or only for the purpose of
> being programmed (as opposed to programming the FPGA afterwards)?  It
> just seems a bit surprising to me, since Xilinx right now seem to have a
> bit of an advantage over Altera in being able to boot from stock SPI
> flash...

EPCS16 = M25P16
EPCS64 = M25P64

Yes, EPCS is ONLY serial flash. The Altera EPCS controller is only SPI 
controller. It is well-known on Altera wiki and Altera forum.

You may use any stock SPI flash to replace EPCS as long as the access 
time met. Though Altera flash programming utility supports only limited 
brands, more SPI flash can be programmed using u-boot or Linux MTD. We 
often boot right out of SPI/EPCS, as it saves cost and space.

There is no difference between Altera and Xilinx in this aspect, except 
for their marketing approach.

Cheers,
Thomas
http://sopc.et.ntust.edu.tw/

  parent reply	other threads:[~2010-11-18  2:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15  8:23 [PATCHv3] drivers/misc: Altera active serial implementation Baruch Siach
2010-11-15  9:33 ` Jiri Slaby
2010-11-15 10:08   ` Baruch Siach
2010-11-15 10:28     ` Jiri Slaby
2010-11-15 13:40       ` Baruch Siach
2010-11-15 14:24         ` Jiri Slaby
2010-11-15 16:19           ` Greg KH
2010-11-16  0:47       ` Indan Zupancic
2010-11-16  5:56         ` Baruch Siach
2010-11-16  7:42           ` H. Peter Anvin
2010-11-16 11:04         ` Alan Cox
2010-11-16 13:09           ` Jiri Slaby
2010-11-17  5:32             ` Baruch Siach
2010-11-17  5:43               ` H. Peter Anvin
2010-11-17  5:48                 ` Baruch Siach
2010-11-17  8:31                   ` Jiri Slaby
2010-11-17 11:08               ` Alan Cox
2010-11-16 11:05         ` Alan Cox
2010-11-17  6:18 ` Thomas Chou
2010-11-17 13:28   ` Baruch Siach
     [not found]   ` <4CE42457.8090001@zytor.com>
2010-11-18  2:15     ` Thomas Chou [this message]
2010-11-18  2:15       ` H. Peter Anvin
2010-11-22  5:57   ` Baruch Siach

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=4CE48C2E.5080502@wytron.com.tw \
    --to=thomas@wytron.com.tw \
    --cc=agersh@rambler.ru \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=baruch@tkos.co.il \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=indan@nul.nu \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nios2-dev@sopc.et.ntust.edu.tw \
    /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;
as well as URLs for NNTP newsgroup(s).