mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
Cc: Wolfgang Draxinger <wdraxinger@darkstargames.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux on XScale 270
Date: Sat, 23 Jun 2007 23:07:11 +0200	[thread overview]
Message-ID: <200706232307.11726.hjk@linutronix.de> (raw)
In-Reply-To: <467D8141.7040604@gmail.com>

Am Samstag 23 Juni 2007 schrieb Dmitry Krivoschekov:
> Wolfgang Draxinger wrote:
> > Typing "Linux XScale 270 or 27x" brings you a lot of pages but not an
>
> Probably "XScale 270" is not the best word combination for this,
> the exact processor name is PXA270 (formerly Intel, now Marvell).
>
> > in depth doc/HOWTO how to compile your own kernel and make a boot
> > image for that arch. The vendor from which I get the XScale sponsored
> > has ready to use Linux images and source on his webpage, but they're
> > kinda old and dusty.
> > http://www.toradex.ch/colibri_downloads/Linux/
> >
> > So what are the steps I've to take, to get a Linux Kernel on a XScale?
>
> Assuming the mainline kernel already includes support for your machine,

It doesn't. I'm currently working on board support for the Toradex Colibri
module, plus one board that uses that module. It works for me now, but 
still needs some testing and cleanup. I'll probably post my patch to the
linux-arm-kernel list next week and try to get it into mainline.

>
> 1. get the latest stable Linux kernel

Yes - please _don't_ use the 2.6.12-something stuff available somewhere
for the Colibri. It contains a serious bug that cost me days to find,
and it's hopelessly out of date.

Step 1.1: Apply my board support patch. Either wait until I post it to
the list or contact me by private mail.

Step 1.2: If your board has an LCD or other extra hardware, add support 
for it in colibri.c.

> 2. compile the kernel:
>     make ARCH=arm CROSS_COMPILE=<your_crosscompiler_prefix>
> <your_machine_name>_defconfig
>     make <kernel_image_name>
>
>     For example, to compile the kernel for Mainstone platform
>     with blob flashed, do the following:
>
>     make ARCH=arm CROSS_COMPILE=arm-linux- mainstone_defconfig
>     make zImage

Depending on your bootloader, you might need to perform extra 
steps, e.g. for U-Boot you need to convert zImage to uImage.

>
> 3. boot the image as appropriate for your bootloader
>
> > It's obvious that I need a cross compiler for ARM, bootloader images
> > and so on, but it's the gory details I'm curios about.
> >
> > Links to HOWTOs, documentation highly appreciated. And probably
> > there's also a better suited maillist than LKML for this, to a
> > pointer to that (if existing) would be nice, too.

I'd recommend to ask this question again on the linux-arm-kernel
list. We shouldn't flood linux-kernel list with arch specific stuff.
It would also be interesting to know which toolchain and/or
distribution you intend to use. Note that you do not only need
a kernel, but also a root file system. The colibri module has only
32MB flash, which means you have to handcraft a small rfs. If you
don't have any plans yet, have a look at www.busybox.net, and
www.scratchbox.org. I used scratchbox to cross compile my kernel
and the packages for my root file system.

>
> linux-arm-kernel@lists.arm.linux.org.uk   - for kernel-specific issues
> linux-arm@lists.arm.linux.org.uk          - for general questions
>
> these are the most appropriate lists for your questions
> (your subscription is required).

True. See you there,
Hans



      reply	other threads:[~2007-06-23 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-23 14:18 Wolfgang Draxinger
2007-06-23 20:23 ` Dmitry Krivoschekov
2007-06-23 21:07   ` Hans-Jürgen Koch [this message]

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=200706232307.11726.hjk@linutronix.de \
    --to=hjk@linutronix.de \
    --cc=dmitry.krivoschekov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wdraxinger@darkstargames.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®