public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: xiangfu <xiangfu.z@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Boot from USB support for Kirkwood SOC
Date: Thu, 11 Jun 2009 15:20:00 +0800	[thread overview]
Message-ID: <4A30B020.7080109@gmail.com> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E201D4A0E07F@SC-VEXCH1.marvell.com>

Prafulla Wadaskar wrote:
> Dear Remy Bohmer
> 
> I am going to start "boot from USB Support" development for kirkwood.
what this "boot from USB Support" means?

I know "boot from nand", 
and I know that the Ingenic CPU, support "boot from USB". is the same meaning?

here is part of JZ4740 cpu data sheet [1]
--
3.7.3   BOOT
Jz4740 support 3 different boot sources depending on BOOT_SEL0 and BOOT_SEL1 pin values.
Table 3-29 lists them.
                             Table 3-29 Boot from 3 boot sources

BOOT_SEL1 BOOT_SEL0                Boot Source
    0         0     Boot from NOR flash at CS4
    0         1     Boot from USB device
    1         0     Boot from 512 page NAND flash at CS1
    1         1     Boot from 2k page NAND flash at CS1
--

[1] ftp://ftp.ingenic.cn/2soc/Jz4740_ds.pdf

> To sync with current USB framework in U-boot, and to reduce some rework at my side (since I am new to this driver).
> May you please provide some guidelines/howto this regard?
> 
> FYI below is details about Kirkwood USB controller:  
> 
> Kirkwood contains a Universal Serial Bus (USB 2.0) port that includes an embedded USB 2.0 PHY.
> The USB 2.0 interface contains a single dual-role controller that can act as a host or a peripheral
> controller (USB controller). A bridge connects the controller to the internal Mbus interface (USB
> bridge).
> Embedded USB 2.0 PHY features include:
> ?? 480 Mbps High Speed (HS)/ 12 Mbps Full Speed (FS) and 1.5 Mbps Low Speed (LS) serial data
> transmission rates
> ?? Synchronization/End-of-Packet (SYNC/EOP) generation and checking
> ?? Data and clock recovery from serial stream on the USB
> ?? Non Return to Zero Invert (NRZI) encoding/decoding with bit stuffing/unstuffing
> ?? Bit stuff error detections
> ?? Bit stuffing/unstuffing; bit stuff error detection
> ?? Holding registers to stage transmit and receive data
> ?? Supports USB 2.0 Test Modes
> ?? Ability to switch between FS and HS terminations/signaling
> ?? For more details, refer to the controller specification document USB-HS High-Speed
> Controller Core Reference.
> 
> Regards..
> Prafulla . .
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot


-- 
Best Regards
Xiangfu Liu

jabber : xiangfu.z at gmail.com
skype  : xiangfu.z

  reply	other threads:[~2009-06-11  7:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10  9:53 [U-Boot] Boot from USB support for Kirkwood SOC Prafulla Wadaskar
2009-06-11  7:20 ` xiangfu [this message]
2009-06-11  7:42   ` Prafulla Wadaskar
2009-06-11  7:50     ` xiangfu
2009-06-11  8:01   ` Wolfgang Denk
2009-06-11  8:10     ` xiangfu
2009-06-15  2:27     ` [U-Boot] MAKEALL, don't have other cross compile xiangfu
2009-06-15  9:44       ` Wolfgang Denk
2009-06-16 15:52         ` xiangfu

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=4A30B020.7080109@gmail.com \
    --to=xiangfu.z@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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