public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Sylvain Munaut <tnt@246tNt•com>
To: Stephen Warren <SWarren@nvidia•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: MPC5200 kernel with IDE *and* FEC?
Date: Wed, 09 Mar 2005 09:02:06 +0100	[thread overview]
Message-ID: <422EAD7E.5090309@246tNt.com> (raw)
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B0056A92CC@hqemmail02.nvidia.com>

Stephen Warren wrote:

>From: Dale Farnsworth [mailto:dale@farnsworth•org] 
>  
>
>>On Tue, Mar 08, 2005 at 05:34:20PM +0000, Stephen Warren wrote:
>>    
>>
>>>I looked at the 2.6.11 kernel.org kernel, and it has MPC5200 IDE
>>>support, but apparently no FEC driver support.
>>>      
>>>
>>Are you sure it has MPC5200 IDE support?  I have yet to see reliable
>>5200 IDE support and haven't seen a 5200 IDE driver for 2.6 at all.
>>    
>>
>
>Not sure, no. Looking at "xconfig", I don't see an option for it. A
>colleague said it did.
>  
>
No it doesn't. Or it's very well hidden ;)
But If you do write it, patches are welcomed.

>We've used IDE (for a DVD-ROM) using the Denx kernel. This didn't have
>DMA suppport, but Freescale gave us a derivate kernel that it, which
>seemed to work well. They said they were going to push this up through
>Denx into the main kernel. Didn't they bother to do this?
>  
>
I guess they mean push it to Denx kernel which IS the main 2.4 kernel 
for MPC5200.
No new platform support will be accepted for 2.4 now. And freescale probably
won't write driver for the tree I maintain since I'm not using the 
official BestComm API.


    Sylvain

  parent reply	other threads:[~2005-03-09  8:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 19:09 MPC5200 kernel with IDE *and* FEC? Stephen Warren
2005-03-08 20:00 ` Wolfgang Denk
2005-03-09  8:02 ` Sylvain Munaut [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-08 20:16 Stephen Warren
2005-03-08 21:27 ` Wolfgang Denk
2005-03-08 17:34 Stephen Warren
2005-03-08 18:10 ` Dale Farnsworth
2005-03-08 20:03 ` 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=422EAD7E.5090309@246tNt.com \
    --to=tnt@246tnt$(echo .)com \
    --cc=SWarren@nvidia$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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