From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: XIP fails on kernels 2.6.12 and higher
Date: Wed, 5 Oct 2005 13:42:53 +0200 [thread overview]
Message-ID: <20051005114253.GA31190@zappa> (raw)
In-Reply-To: <6934efce05092915519ffe76c@mail.gmail.com>
* Jared Hulbert <jaredeh@gmail.com> [Thu, Sep 29, 2005 at 03:51:50PM -0700]:
> Alexey. My OSK got destroyed. Can somebody confirm xipImage of
> 2.6.12 fails to boot where 2.6.11 runs on a different hardware
> platform?
http://lists.infradead.org/pipermail/linux-mtd/2005-September/013536.html
Is about the same. I can't get it running on 2.6.13.
I dont know anymore how I got 2.6.12 working or digged around the
problems but IIRC there where several regarding the XIP stuff.
Konsti
next prev parent reply other threads:[~2005-10-05 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:08 XIP fails on kernels 2.6.12 and higher Korolev, Alexey
2005-09-22 17:20 ` Nicolas Pitre
2005-09-29 22:51 ` Jared Hulbert
2005-10-05 11:42 ` Konstantin Kletschke [this message]
2005-10-12 19:05 ` Jared Hulbert
2005-10-12 20:23 ` Nicolas Pitre
2005-10-12 20:49 ` Konstantin Kletschke
2005-10-12 21:22 ` Jared Hulbert
2005-10-05 11:45 ` Konstantin Kletschke
2005-10-06 13:31 ` Konstantin Kletschke
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=20051005114253.GA31190@zappa \
--to=lists@ku-gbr.de \
--cc=linux-mtd@lists.infradead.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.