From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Russell King <rmk@arm.linux.org.uk>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Make spitz compile again
Date: Tue, 01 Nov 2005 21:46:52 +0000 [thread overview]
Message-ID: <1130881612.8489.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20051101200516.GA7172@elf.ucw.cz>
On Tue, 2005-11-01 at 21:05 +0100, Pavel Machek wrote:
> Hi!
>
> > > This is what I needed to do after update to latest linus
> > > kernel. Perhaps it helps someone.
> > >
> > > Signed-off-by: Pavel Machek <pavel@suse.cz>
> > >
> > > , but it is against Richard's tree merged into my tree, so do not
> > > expect to apply it over mainline. Akita code movement is needed if I
> > > want to compile kernel without akita support...
> >
> > This is an update of my tree against 2.6.14-git3:
> >
> > http://www.rpsys.net/openzaurus/temp/total-2.6.14-git3-r0.patch.gz
>
> I did compile fixing, but it still will not boot. With neither my
> config, not with yours. Just blank screen. Any ideas?
>
> > http://www.rpsys.net/openzaurus/temp/total-2.6.14-git3-r0-defconfig-cxx00
I've worked out a patch to revert the change that broke things for c7x0:
http://www.rpsys.net/openzaurus/patches/revert_bootmem-r0.patch
I'd be interested to know if this helps your spitz kernel as its gets
c7x0 working again. Obviously the next step is to work out why this
breaks things but reverting it gets my Zaurus dev tree working again
which stops users c7x0 complaining :)
Richard
next prev parent reply other threads:[~2005-11-01 21:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 13:42 Make spitz compile again Pavel Machek
2005-10-31 15:45 ` Richard Purdie
2005-11-01 19:31 ` Pavel Machek
2005-11-01 20:10 ` Richard Purdie
2005-11-01 20:37 ` Pavel Machek
2005-11-01 20:39 ` Pavel Machek
2005-11-01 20:40 ` Pavel Machek
2005-11-01 20:05 ` Pavel Machek
2005-11-01 20:19 ` Richard Purdie
2005-11-01 21:46 ` Richard Purdie [this message]
2005-11-01 22:14 ` Russell King
2005-11-01 22:54 ` Richard Purdie
2005-11-02 11:10 ` Pavel Machek
2005-11-02 12:51 ` Pavel Machek
2005-11-02 13:47 ` Richard Purdie
2005-11-02 13:52 ` Pavel Machek
2005-11-02 14:44 ` Richard Purdie
2005-10-06 7:16 ` spitz autorepeat Pavel Machek
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=1130881612.8489.33.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rmk@arm.linux.org.uk \
/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