public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [patch] csb337 board support (ARM at91rm9200)
Date: Mon, 29 Jun 2009 23:16:01 +0200	[thread overview]
Message-ID: <20090629211601.GE23292@game.jcrosoft.org> (raw)
In-Reply-To: <200906282320.51697.david-b@pacbell.net>

> > >   - USB didn't work; the software wouldn't detect usb-storage devices.
> > >     So it's not yet enabled.
> >
> > what is the power on the USB?
> 
> I don't understand the question.  5V of course.  Not switchable.
is the usb provide enough power to supply the usb key
> 
>  
> > >   - There seems to be some issue copying lots of data from NOR flash.
> > >     It works OK in chunks of up to 512 KB or so, but copying a kernel
> > >     (1.4 MB) failed ... copying *way* over 15 MBytes, and trashing
> > >     the DRAM image of U-Boot that was running.  (Compiler issue?)
> >
> > Clock issue ot RAM timing issue
> 
> Doesn't quite make sense.  Something clobbered a termination
> condition, which would be in a register, or at worst in cache.
> 
> How would RAM timing cause breakage?  The data copied was
> correct, in smaller chunks, and the termination condition
> wasn't stored in RAM.  Or a clock issue, considering all the
> relevant cycles are inside the arm920t core?
> 
> I like the "compiler issue" theory better.  :(
> 
>  
> > >  board/csb337/u-boot.lds  |   56 +++++++++++
> >
> > no need please remove
> 
> In mainline u-boot it seems to be needed.  Can you maybe push your
> first set of patches to Wolfgang, which consolidate all
> that stuff?
the arm work need to be based on u-boot-arm tree
> 
> 
> > > +#if defined(CONFIG_DRIVER_ETHER) && defined(CONFIG_CMD_NET)
> > it will be better ot manage this in the config header
> 
> You mean by defining an otherwise needless symbol,
> along the lines of CONFIG_SYS_AT91RM9200_LXT_PHY?
CONFIG_DRIVER_EHTER will be enough
> 
> Probably simpler just always include those few lines,
> and not support building without Ethernet.
> 
> 
> > > +
> > > +/* The AT91 lxt972 glue modified the original lxt971 code by
> > > + * changing names and generalizing a bit.  So we use "lxt972"
> > > + * names here even though the CSB337 has an lxt971 chip.
> > > + */
> > > +extern unsigned char lxt972_InitPhy(AT91S_EMAC *mac);
> > > +extern unsigned lxt972_IsPhyConnected(AT91S_EMAC *mac);
> > > +extern unsigned char lxt972_GetLinkSpeed(AT91S_EMAC *mac);
> > > +extern unsigned char lxt972_AutoNegotiate(AT91S_EMAC *mac, int *status);
> > :(
> > please a header
> 
> I'll stick it in hardware.h ... you can remove similar decls
> from other rm9200 boards then.
a phy header will be better IMHO
> 
> > > +
> > > +#if 0
> > please 
> > if CONFIG_CMD_USB
> > > +/* REVISIT:  USB failed to enumerate devices of any kind ... sw issues */
> 
> An #if 0 won't work without completely re-whacking things.
> 
> Right now the commands kick in *MUCH LATER* depending on
> whether the driver is available.  And here, the driver
> (CONFIG_USB_OHCI_NEW driver) and its support is disabled
> since it's not working...
so move it

Best Regards,
J.

  reply	other threads:[~2009-06-29 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 21:58 [U-Boot] [patch] csb337 board support (ARM at91rm9200) David Brownell
2009-06-25 21:56 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-29  6:20   ` David Brownell
2009-06-29 21:16     ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-06-29 21:46       ` David Brownell
2009-06-29 22:44         ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-10 22:43 ` 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=20090629211601.GE23292@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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