public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Simon Yang <bestwish.simon@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot kernel parameters
Date: Fri, 17 Feb 2006 14:47:54 +0800	[thread overview]
Message-ID: <1c3e00040602162247j58a1fba0k@mail.gmail.com> (raw)
In-Reply-To: <43F33693.2030808@sandburst.com>

Hi Travis,

Thanks for your reply. I still have a question, for rgmii mode the bits 11:9
of phy reg 0x17 should be 001 which means the I/O pin operate from 2.5V,
default is 3.3V if the value of bits 11:9 is 000, so whether I should
set reg 0x17 to 1200.

The cpu we use is MPC8349E, I set the reg ECNTRL to 0x00001010 , I can
meature the signals on TSEC1_GTX_CLK, Tx_EN and Tx_D[0:3], the RGMII should
operate on 2.5v but the voltage I meature on Tx_D is 3.3v , so there is a
problem  that the value of reg SICRH(in local memory offset is 0x118) is
always 00000002(GMII mode and RGMII mode), but in the datasheet of MPC8349E
the bits 30 and 31of reg SICRH (TSOBI1 and TSOBI2) controls the output
buffer impedance of the TSEC1and TSEC2 output signals, so I think the value
I get is not what I expected. Cany anybody tell me how the reg SICRH get
this value? Seems SICRH only use in /cpu/mpc83xx/cpu_init.c file. Thanks a
lot!


2006/2/15, Travis B. Sawyer <tsawyer@sandburst.com>:
>
> Simon Yang wrote:
> > Dear All,
> >
> > Now I am working on CIS8201 PHY for RGMII mode, I have modified Reg
> > 23(0x17h) from 0000 to 1300, but CIS8201 doesn't work under RGMII
> > mode, are there other registers I need to set? Please give me your
> > comment. Thanks a lot!
> >
> Simon:
> If you're using the ocotea, phy reg 0x17 should be written with 0x1000
> for rgmii mode, not 0x1300.  0x300 enables clock skewing for boards with
> short etch, like the Sandburst Metrobox and Karef boards.  The ocotea
> has full length etch and doesn't (or rather should not) use clock skewing.
>
>
> Das U-Boot current source should 'just work' on the ocotea board.
>
> (I can't verify the current source as I haven't done a git sync since
> Stefan merged/fixed the 4xx files, too many time constraints here at
> work, so I'm working with an 'older' tree).
>
> -travis
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060217/3c5a4b9c/attachment.htm 

  parent reply	other threads:[~2006-02-17  6:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 18:14 [U-Boot-Users] u-boot kernel parameters Bizzu
2006-02-07 18:55 ` S. Egbert
2006-02-07 19:05   ` Tattone Tattone
2006-02-07 20:55     ` Wolfgang Denk
2006-02-07 21:23       ` Tattone Tattone
2006-02-07 23:39         ` Wolfgang Denk
2006-02-07 21:56       ` Stefan Roese
2006-02-07 22:22         ` Bizzu
2006-02-08  6:58         ` Stefan Roese
2006-02-08 13:27           ` Tattone Tattone
2006-02-15 10:56             ` Simon Yang
2006-02-15 14:11               ` Travis B. Sawyer
2006-02-15 18:32                 ` Bizzu
2006-02-17  6:47                 ` Simon Yang [this message]
2006-02-08 18:04           ` Bizzu
2006-02-07 20:54   ` Wolfgang Denk
2006-02-07 23:15     ` Bizzu
2006-02-07 23:42       ` Wolfgang Denk
2006-02-08 10:24       ` Andreas Schweigstill
2006-02-08 13:24         ` Tattone Tattone
2006-02-08  4:45     ` S. Egbert
2006-02-07 20:51 ` Wolfgang Denk

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=1c3e00040602162247j58a1fba0k@mail.gmail.com \
    --to=bestwish.simon@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