From: Martin Costabel <costabel@wanadoo.fr>
To: Ani Joshi <ajoshi@shell.unixbox.com>
Cc: Andreas Tobler <toa@pop.agri.ch>,
Jack Howarth <howarth@bromo.med.uc.edu>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: bk 2.4-test7 broken
Date: Wed, 16 Aug 2000 21:46:28 +0200 [thread overview]
Message-ID: <399AEF94.A927EE72@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.10.10008160749260.28397-100000@shell.unixbox.com
Ani Joshi wrote:
>
> FWIW, 2.4.0-test7-pre4 (kernel.org) boots here on a 603e. Few minor
> fixing up needed for the build, perhaps one of you should do a bk vs.
> kernel.org diff and find your problem.
Seems to have been the right idea. By putting the arch/ppc and
include/asm-ppc directories from linux-pmac-devel into my linux-bk-devel
copy and then applying the kernel.org test7-pre4 patch (plus some minor
fiddling), I have now a kernel that boots, calls itself 2.4.0-test7 and
still has the new input layer from the bk-devel tree.
It also should have the latest patches for RTC, but I cannot test this,
because I get
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory
just as with Paul's 2.4.0-test6 kernel. I am using devfs, so the
/dev/rtc device should be created automagically, and in 2.4.0-test5 this
worked.
What the problem was is hard to say, because there are now a lot of
diffs to the bk-devel tree.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-16 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 3:04 bk 2.4-test7 broken Jack Howarth
2000-08-15 11:28 ` Martin Costabel
2000-08-15 18:20 ` Andreas Tobler
2000-08-15 21:47 ` Andreas Tobler
2000-08-16 7:09 ` Martin Costabel
2000-08-16 14:51 ` Ani Joshi
2000-08-16 19:46 ` Martin Costabel [this message]
2000-08-15 19:28 ` Michel Lanners
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=399AEF94.A927EE72@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=ajoshi@shell.unixbox.com \
--cc=howarth@bromo.med.uc.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toa@pop.agri.ch \
/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).