LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wade Farnsworth <wfarnsworth@mvista.com>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] ppc32: Support for Freescale PQ2FADS
Date: 06 Apr 2006 09:06:18 -0700	[thread overview]
Message-ID: <1144339578.11172.19.camel@rhino.az.mvista.com> (raw)
In-Reply-To: <20060406180517.36ad1b7d@vitb.ru.mvista.com>

On Thu, 2006-04-06 at 07:05, Vitaly Bordug wrote:
> 
> Though I doubt if new boards are accepting to ppc/ currently, it's nice to have a patch 
> available. BTW, I suggest to use phy abstraction and updated fs_enet (submitted here recently)

I'll look into that.

> 
> Some more notes below.

<snip>
> > +CONFIG_INPUT=y
> 
> This is useless for the board iirc.
<snip>
> >
> > +CONFIG_SOUND_GAMEPORT=y
> ditto.

Yes, you're right.  I'm not sure why I had those enabled.

<snip>
> > +CONFIG_USB_ARCH_HAS_HCD=y
> > +CONFIG_USB_ARCH_HAS_OHCI=y
> 
> Not sure this is required as well.

I'll disable this as well.

<snip>

> > +#ifdef CONFIG_PQ2FADS
> > +#define F2_RXCLK	13
> > +#define F2_TXCLK	14
> > +#else
> >  #define F2_RXCLK	15
> >  #define F2_TXCLK	16
> > +#endif
> >  
> Hmm, this should go into the board-specific header - here should exist just a "reasonable default" (pq2ads.h in this context). 
> 
> 
> >  /* FCC3 Clock Source Configuration.  These can be redefined in the board specific file.
> >     Can only choose from CLK13-16 */
> > +#ifdef CONFIG_PQ2FADS
> > +#define F3_RXCLK	15
> > +#define F3_TXCLK	16
> > +#else
> >  #define F3_RXCLK	13
> >  #define F3_TXCLK	14
> > +#endif
> >  
> ditto.

Ok, I'll move these defines into pq2ads.h

Thanks for the feedback.  I'll make the changes and resubmit.

-Wade Farnsworth

  reply	other threads:[~2006-04-06 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 23:54 [PATCH] ppc32: Support for Freescale PQ2FADS Wade Farnsworth
2006-04-06 14:05 ` Vitaly Bordug
2006-04-06 16:06   ` Wade Farnsworth [this message]
2006-04-06 16:44     ` Wade Farnsworth
2006-04-13 16:16 ` Wade Farnsworth

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=1144339578.11172.19.camel@rhino.az.mvista.com \
    --to=wfarnsworth@mvista.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=vbordug@ru.mvista.com \
    /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