All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: 陈晓 <chenzl92@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] How to Adapt ARM I-pipe patch to S3C6410
Date: Sat, 24 Dec 2011 14:36:59 +0100	[thread overview]
Message-ID: <4EF5D57B.2080305@domain.hid> (raw)
In-Reply-To: <CADwQ9Q51ze5gtxU9ObHqGxW8nJpM--eQhWvzmf5y2MhcxN0xXQ@mail.gmail.com>

On 12/24/2011 03:10 AM, 陈晓 wrote:
> sorry for the mistake,my ipipe-patch is
> adeos-ipipe-2.6.37.6-arm-1.18-03   ,and where can I get the new
> "HowTo" as it maybe out of date.
> As I said,I add the printascii function in the begin of
> start_kernel(),but it didn't print out ,so I believe it didn't go to
> the start_kernel. I also add the printascii function to the
> arch/arm/kernel/head.S,I found when it run to "enable the mmu" it
> stopped. I believe the .config file works well before I patch the
> xenomai .I also believe the xenomai has nothing to do with the setup
> of hardware before the kernel startup.
> 

There is no updated version of the howto. But the only wrong thing is
the part about multiplexed interrupts.

You should try printascii with a non-patched kernel to verify that
printascii works for the board you use.

As for using printascii around the place where the mmu is enabled, have
you read the following comment in the kernel sources:

/*
 * Enable the MMU.  This completely changes the structure of the visible
 * memory space.  You will not be able to trace execution through this.
 * If you have an enquiry about this, *please* check the linux-arm-kernel
 * mailing list archives BEFORE sending another post to the list.

Anyway, as early in the boot process the I-pipe patch does not change
anything, so, your problem does not come from the I-pipe patch. Have you
tried the exact same config you use with the patched kernel with an
unpatched kernel?

-- 
                                                                Gilles.



  reply	other threads:[~2011-12-24 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-24  2:10 [Xenomai-help] How to Adapt ARM I-pipe patch to S3C6410 陈晓
2011-12-24 13:36 ` Gilles Chanteperdrix [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-19  1:38 陈晓
2011-12-19 11:38 ` Gilles Chanteperdrix
     [not found]   ` <CADwQ9Q5U8Eftm4ok_x_YHSAHY36ah=WsYwDcvuVzpKMdXvAjKw@domain.hid>
2011-12-22 10:00     ` Gilles Chanteperdrix

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=4EF5D57B.2080305@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=chenzl92@domain.hid \
    --cc=xenomai@xenomai.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 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.