PQ2FADS Support

PQ2FADS Support

[Kevin A. Sapp]

Hello,

I am working with a Motorola PQ2FADS board.  I currently
have a "free" teaser distribution from a vendor that works for
the board.  The FADS board is not the ultimate target.

I tried to use the latest ATM driver for the PQ2, but have
lots of unresolves due to the vendor mods in the low level
stuff.

I would like to use the eldk, but, when I pulled down the
latest CVS version this morning and try to configure there
is not an option for PQ2FADS.

I would rather go with the ELDK since it is has a larger
tool set and support is through the community.

So, does anyone have a .config and associated support
for PQ2FADS-VR ?  (8275-VR 266/166/66)
Suggestions?

Thanks
Kevin


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: PQ2FADS Support

[Wolfgang Denk]

In message <3F8FFB74.2030609@catapult.com> you wrote:
>
> I would like to use the eldk, but, when I pulled down the
> latest CVS version this morning and try to configure there
> is not an option for PQ2FADS.

I think this is a misunderstanding. The ELDK is a  _toolkit_,  not  a
kernel  distribution.  (Yes,  the  ELDK  does  contain a Linux kernel
source tree, too - the current version of the ELDK contains our 2.4.4
kernel tree).

But if you're looking at specific board support, you  can  use  _any_
kernel source tree in combination with the ELDK tools.


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
1 1 was a race-horse, 2 2 was 1 2. When 1 1 1 1 race, 2 2 1 1 2.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

pq2fads support...

[Alexandros Kostopoulos]

Hello Scott and all,

In your patch for the pq2fads support, the device tree seems to be missing  
a memory node, for which dtc complains loudly. Is this board tested to  
boot with these patches (because I'm now using this as a template for my  
board - with your patchset applied to Paul's git)

thanks a lot

Alex

PS. What's about this new cpm-serial driver? is this supposed to be a  
replacement for cpm_uart?

Re: pq2fads support...

[Scott Wood]

On Fri, Jul 27, 2007 at 03:24:08PM +0300, Alexandros Kostopoulos wrote:
> In your patch for the pq2fads support, the device tree seems to be missing  
> a memory node, for which dtc complains loudly. Is this board tested to  
> boot with these patches (because I'm now using this as a template for my  
> board - with your patchset applied to Paul's git)

Sorry about that -- dtc complains about a lot of silly things, falsely
assuming that the result is intended to be a complete tree ready for
passing to Linux (which is rarely true).  I'd been running with a patch
to remove some of those checks, but it got rejected, and I forgot to
stick the templates back into the dts.

The next patchset will have a dts that works with current dtc; in the
meantime, you can add the -f flag to dtc in arch/powerpc/boot/wrapper, or
add the missing nodes based on the mpc8272ads device tree (the actual
information will be filled in by the bootwrapper).

> PS. What's about this new cpm-serial driver? is this supposed to be a  
> replacement for cpm_uart?

No, it's a minimal driver for the bootwrapper.

-Scott

Re: pq2fads support...

[Alexandros Kostopoulos]

Thanks for your reply, Scott,

one question though: I am NOT using the bootwrapper, I'm instead feeding  
dtb and uImage directly to u-boot. This probably means that I should fill  
in lots of stuff manually into dts, right? But, (and please forgive my  
ignorance) who does actually fill in stuff (like e.g. clock-frequency or  
bus-frequency), except, of course, from the trivial modifications u-boot  
does to dtb? The wrapper script seems to do nothing more that simply  
running dtc on dts.

Thanks again

Alex

On Fri, 27 Jul 2007 19:35:29 +0300, Scott Wood <scottwood@freescale.com>  
wrote:

> On Fri, Jul 27, 2007 at 03:24:08PM +0300, Alexandros Kostopoulos wrote:
>> In your patch for the pq2fads support, the device tree seems to be  
>> missing
>> a memory node, for which dtc complains loudly. Is this board tested to
>> boot with these patches (because I'm now using this as a template for my
>> board - with your patchset applied to Paul's git)
>
> Sorry about that -- dtc complains about a lot of silly things, falsely
> assuming that the result is intended to be a complete tree ready for
> passing to Linux (which is rarely true).  I'd been running with a patch
> to remove some of those checks, but it got rejected, and I forgot to
> stick the templates back into the dts.
>
> The next patchset will have a dts that works with current dtc; in the
> meantime, you can add the -f flag to dtc in arch/powerpc/boot/wrapper, or
> add the missing nodes based on the mpc8272ads device tree (the actual
> information will be filled in by the bootwrapper).
>
>> PS. What's about this new cpm-serial driver? is this supposed to be a
>> replacement for cpm_uart?
>
> No, it's a minimal driver for the bootwrapper.
>
> -Scott

Re: pq2fads support...

[Scott Wood]

Alexandros Kostopoulos wrote:
> Thanks for your reply, Scott,
> 
> one question though: I am NOT using the bootwrapper, I'm instead 
> feeding  dtb and uImage directly to u-boot. This probably means that
> I should fill  in lots of stuff manually into dts, right?

No, u-boot should fill in the same stuff.  It may require the empty
fields to be there, though (it definitely requires it if you're using
the old, non-libfdt code -- if you are, you should also remove the 
/chosen node, or else you'll get two of them).

> But, (and please forgive my  ignorance) who does actually fill in
> stuff (like e.g. clock-frequency or  bus-frequency), except, of
> course, from the trivial modifications u-boot  does to dtb? The
> wrapper script seems to do nothing more that simply  running dtc on
> dts.

In the bootwrapper case, it's the code in cuboot-pq2.c and devtree.c. 
In the no-bootwrapper case, it's u-boot.

-Scott