linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Asemann <peter.asemann@web.de>
To: linuxppc-embedded@ozlabs.org
Subject: eldk: compiling linux for custom hardware
Date: Fri, 04 Feb 2005 16:26:07 +0100	[thread overview]
Message-ID: <4203940F.2010109@web.de> (raw)

I'm going to compile embedded power pc linux for a custom hardware.
I use the Denx ELDK.
The Linux Kernel configuration (make menuconfig) asks what machine type
to compile Linux for.
So I have the problem that I do not know which option to choose ("none"
is not an option in the dialogue) and that I also do not know what
choosing one of the existing options actually changes behind the scenes.
I'd like a Linux to drop out that supports my MPC875 chip, works with
the LXT 970A ethernet PHY chip and (if possible) the ISP1301
USB-on-the-go USB chip the board has and supports a serial terminal via
SCC4 via the RXD4/TXD4 signals.

Any hint will be appreciated,

best regards,

Peter Asemann

             reply	other threads:[~2005-02-04 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 15:26 Peter Asemann [this message]
2005-02-04 17:21 ` eldk: compiling linux for custom hardware 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=4203940F.2010109@web.de \
    --to=peter.asemann@web.de \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).