ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] LTIB port for mcp8270


From: Stuart Hughes
Subject: Re: [Ltib] LTIB port for mcp8270
Date: Thu, 31 May 2007 18:18:33 +0100

Hi Joseph,

LTIB has a number of 603e toolchains that should be usable (glibc and
uclibc), so I think we're okay with those.

The main thing is to get hold of a kernel source and kernel config file.
Once those are available creating the BSP config should be easy.  The
fun starts when you try to boot.  Theoretically if the kernel is a known
good booter, it should "just work", but I think most people know that
the path of true development rarely runs that smoothly.

I'll take a look to see if I can find that PCS BSP, I should have it.
I'll let you know what I find.  This is a project for me "out of hours"
and so I'll do my best, but no promises.  I don't have that hardware, so
hopefully you can help with the testing.

Regards, Stuart

On Thu, 2007-05-31 at 11:04 -0400, Joseph E. Sacco, Ph.D. wrote: 
> Stuart,
> 
> This is going to be fun... :-)
> 
> Two things to consider:
> (1) PQ2FADS_20041214-3.0
> The original Freescale BSP for the mcp82xx family. This BSP was used
> with the "Package Creation Suite" to build a 2.4.24 kernel. 
> 
> I have in hand the kernel source and a working config file.
> 
> 
> (2) MPC8272ADS_K26
> This Freescale BSP, written for a different mcp82xx family member, has a
> slightly newer tool chain 
> 
>    gcc-3.4.3-glibc-2.3.3.tar.gz
> 
> that should work with any chip with a 603e core.
> 
> 
> -Joseph
> 
> ======================================================================
>  
> On Thu, 2007-05-31 at 15:10 +0100, Stuart Hughes wrote:
> > Hi Joseph,
> > 
> > If have any known starting point, including a 2.4 kernel that would be
> > okay and maybe save you some effort.  Just a thought.
> > 
> > Regards, Stuart
> > 
> > On Thu, 2007-05-31 at 09:46 -0400, Joseph E. Sacco, Ph.D. wrote:
> > > Stuart,
> > > 
> > > I understand the intent of Freescale to focus on newer devices.  I also
> > > understand the concept of servicing what you sell. 
> > > 
> > > That being said... I should have some spare cycles this weekend.  I will
> > > take a look at crafting a 2.6.x kernel for mcp82xx devices. 
> > > 
> > > 
> > > Regards,
> > > 
> > > 
> > > -Joseph
> > > 
> > > ============================================================================
> > > 
> > > On Thu, 2007-05-31 at 08:36 +0100, Stuart Hughes wrote:
> > > > Hi Joseph,
> > > > 
> > > > I think from Freescale's point of view that's right as for "official"
> > > > BSPs they'll tend to concentrate more on newer devices.
> > > > 
> > > > As I mentioned before, there exists an external LTIB project, if you can
> > > > contribute a kernel+kernel config file, I'm happy to help you put
> > > > together a BSP for it.
> > > > 
> > > > Regards, Stuart
> > > > 
> > > > On Wed, 2007-05-30 at 14:56 -0400, Joseph E. Sacco, Ph.D. wrote:
> > > > > I pinged Freescale support. The response is shown below.
> > > > > 
> > > > > Interesting...
> > > > > 
> > > > > 
> > > > > -Joseph
> > > > > 
> > > > > ============================================================
> > > > > Dear Joseph Sacco, 
> > > > > 
> > > > > In reply to your Service Request SR 1-362864531: 
> > > > > 
> > > > > Thanks for your patience speaking with marketing manager I was told.  
> > > > > We are not road mapping a revised Linux BSP for the MPC82xx that would
> > > > > include the LTIB port.  Our customers would need to use one of our 3rd
> > > > > parties for a customization tool similar to LTIB or PCS on the MPC82xx
> > > > > platforms. 
> > > > > 
> > > > > I hope this helps with your question,
> > > > > 
> > > > > Thank you for your interest in Freescale Semiconductor products and 
> > > > > for
> > > > > the opportunity to serve you. 
> > > > > 
> > > > > Should you need to contact us with regard to this message, please see
> > > > > the notes below.
> > > > > 
> > > > > Best Regards,
> > > > > Pamela 
> > > > > Technical Support
> > > > > Freescale Semiconductor
> > > > > 
> > > > 
> > 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]