From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: Sato Daisuke <densuke@fuga.jp>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: benh's kernel is unable to compile.
Date: Tue, 30 Oct 2001 17:57:41 +1300 [thread overview]
Message-ID: <3BDE3345.4020105@waitaki.otago.ac.nz> (raw)
In-Reply-To: 3BDE0FEB.1050206@waitaki.otago.ac.nz
Bryce McKinlay wrote:
> FYI I built 2.4.14-pre2-ben0 out of rsync about 2 hours ago and it seems
> to be working. It does get some IDE errors about lost IRQs during bootup
> that didn't happen with 2.4.13-ben0. Eventually it said "ide0: reset"
> and now appears to be working normally. This is on a Powebook G4.
Correction: DMA isn't working.
regards
Bryce.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-30 4:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 1:24 benh's kernel is unable to compile Sato Daisuke
2001-10-30 2:26 ` Bryce McKinlay
2001-10-30 4:57 ` Bryce McKinlay [this message]
2001-10-30 5:10 ` Sato Daisuke
2001-10-30 9:17 ` Benjamin Herrenschmidt
2001-10-30 9:59 ` Bryce McKinlay
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=3BDE3345.4020105@waitaki.otago.ac.nz \
--to=bryce@waitaki.otago.ac.nz \
--cc=densuke@fuga.jp \
--cc=linuxppc-dev@lists.linuxppc.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 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).