From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Denx vs kernel.org
Date: Thu, 8 Dec 2005 12:31:49 -0200 [thread overview]
Message-ID: <20051208143149.GA14554@dmt.cnet> (raw)
In-Reply-To: <20051206211459.E8976353F54@atlas.denx.de>
On Tue, Dec 06, 2005 at 10:14:59PM +0100, Wolfgang Denk wrote:
> In message <20051206164212.82779.qmail@web33505.mail.mud.yahoo.com> you wrote:
> > I'm looking at embedding linux into a PowerPC-based
> > system. I found the DENX website to be very helpful,
> > but I'm struggling to understand a few items:
>
> It would be helpful if you precisely stated which of the misc trees
> you are talking about.
>
> > 1) The source from kernel.org appears to have support
> > for the powerpc (arch/powerpc/8xx_io). But when using
> > 'make xconfig' I cannot select PowerPC from the list
> > of processors. Is this just a limitation on the the
> > configuration utility?
>
> Seems like you are trying to use the linux-2.6-denx tree and forgot
> to pass a "ARCH=ppc" argument to "make" (and did not set "ARCH=ppc"
> in your shell environment either).
>
> > 2) What is the difference between the sources on DENX
> > and kernel.org? Are there other places where PPC
>
> We have some stuff added which was submitted as patches to the list
> but not all of this has been accepted for or merged into the
> kernel.org tree yet.
Hi Wolfgang,
Is there a list of your fixes anywhere? Is the linux-2.6-denx tree
public?
next prev parent reply other threads:[~2005-12-08 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 16:42 Denx vs kernel.org Matt Jerdonek
2005-12-06 16:58 ` White
2005-12-06 21:14 ` Wolfgang Denk
2005-12-08 14:31 ` Marcelo Tosatti [this message]
2005-12-08 22:27 ` Kumar Gala
2005-12-08 23:17 ` 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=20051208143149.GA14554@dmt.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.