linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Oliver Rutsch <orutsch@sympatec.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: STK5200 pci_enable_device problem
Date: Mon, 27 Aug 2007 20:58:53 +0200	[thread overview]
Message-ID: <20070827185853.76E3A24047@gemini.denx.de> (raw)
In-Reply-To: Your message of "Mon, 27 Aug 2007 08:25:03 +0200." <46D26E3F.8040309@sympatec.com>

In message <46D26E3F.8040309@sympatec.com> you wrote:
> 
>  >> It's not so easy to compile the PLX drivers on the 4.1 ELDK because of
>  >> missing headers in the ppc architecture. I managed to build the drivers
>  >> for the 2.6.19 kernel and I was able to work with the card except the
>  >> DMA routines (still working on this issue).
>  >
>  > WHy don't you use the arch/powerpc configuration, then? Note that the
>  > STK5200 has never been supported in a  2.6  kernel  with  a  arch/ppc
>  > configuration.
>  >
> 
> Because I found at least a lite5200 configuration in the 4.1 ELDK 
> (2.6.19.2 kernel) in the ARCH/ppc architecure. With ARCH/powerpc I only 

You will find many completely unsupported board configurations in the
kernel.org tree, too. The fact that somethign  is  present  does  not
mean anything.

> Is there support for the TQM5200 and the STK5200 with ARCH/powerpc in 
> newer kernels? I'm still using the 3.1.1 ELDK for the TQM5200 as it have 
> everything I need and I don't need to use the PLX card in this board 
> (although it would have been nice if I got it working...).

The TQM5200 / STK5200 are supported in our linux-2.6-denx  tree  with
an  arch/powerpc  configuration; also lite5200b. Note that - like all
MPC5200 support in the 2.6 kernel - this is all work in progress.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
It is dangerous to be right on a subject  on  which  the  established
authorities are wrong.                                    -- Voltaire

  reply	other threads:[~2007-08-27 18:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23  5:42 STK5200 pci_enable_device problem Mustafa Cayır
2007-08-23  7:24 ` Oliver Rutsch
2007-08-26 21:10   ` Wolfgang Denk
2007-08-27  6:25     ` Oliver Rutsch
2007-08-27 18:58       ` Wolfgang Denk [this message]
2007-08-27 11:08   ` Mustafa Cayir
2007-08-27 19:14     ` Wolfgang Denk
2007-08-28  8:51       ` Mustafa Cayir
2007-08-29  6:02         ` Oliver Rutsch
2007-08-29  7:49           ` Wolfgang Denk
2007-08-29 12:52             ` Oliver Rutsch
2007-08-29 23:31               ` Wolfgang Denk
2007-08-30  9:19                 ` Oliver Rutsch
2007-08-31  5:38                   ` Mustafa Cayir
2007-09-01 23:23                   ` Wolfgang Denk
2007-08-26 21:08 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2007-09-14 11:38 Mustafa Cayır
2007-09-14 12:53 ` Oliver Rutsch

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=20070827185853.76E3A24047@gemini.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=orutsch@sympatec.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;
as well as URLs for NNTP newsgroup(s).