linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ryuichi Oikawa <roikawa@rr.iij4u.or.jp>
To: jk@espy.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Blue G3 and machine check
Date: Sat, 10 Apr 1999 01:12:37 +0900	[thread overview]
Message-ID: <19990410011237E.roikawa@rr.iij4u.or.jp> (raw)
In-Reply-To: Your message of "Thu, 8 Apr 1999 22:58:36 -0700" <v04204d03b333436e691f@[206.163.71.146]>


From: Joel Klecker <jk@espy.org>
Subject: Re: Blue G3 and machine check
> >>ftp://ppc.linux.or.jp/pub/users/oikawa/linux-pmac/bluemacg3/vmlinux-2. 
> >>2.1-challenger2.gz
> >>I was given many useful advice on this by Benjamin Herrenschmidt.
> >
> >Any chance you could put up a proper diff for the sources used to build that
> >kernel? I'd really appreciate it. Thanks.
> 
> Since I received absolutely no response to this, let me elaborate. I 
> have had success in booting and running a system with this kernel, 
> but its config does not suit my needs, therefore I really would like 
> to have the source. The pseudo-diffs in the message I originally 
> replied to do not seem to be enough to produce a working kernel, are 
> they really all of the changes?
 Yes, that was all.

> If they are, then I would like a copy 
> of the .config so I can see what the differences in configuration 
> are. Thanks again.
I thought it was almost default...  Then I'll make complete
diff to 2.2.1 kernel from samba and put it later on 
  ftp://ppc.linux.or.jp/pub/users/oikawa/linux-pmac/bluemacg3/ 
But please note that
 - it is minimal workaround and should not be used for long time
 - ultraATA chip(CMD646) driver has not been ported yet, so that
   if you need it, you have to rewrite yourself. But usual ATA bus,
   which CDROM is connected, does work.
 - it is a diff to kernel 2.2.1, not to latest one


Regards,

Ryuichi Oikawa
roikawa@rr.iij4u.or.jp

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-04-09 16:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-14 13:35 Blue G3 and machine check Benjamin Herrenschmidt
1999-03-15 16:42 ` Ryuichi Oikawa
1999-03-15 17:09   ` Geert Uytterhoeven
1999-03-24  9:30 ` Gabriel Paubert
1999-03-24 23:12   ` Paul Mackerras
1999-03-25 11:20     ` Gabriel Paubert
1999-03-25 16:46       ` Apple Job Posting and Good News for LinuxPPC developers Kevin B. Hendricks
1999-03-25 19:12         ` David Edelsohn
1999-03-26 11:31           ` Gabriel Paubert
1999-03-26 16:13             ` David Edelsohn
1999-03-27  6:27               ` Guy Sotomayor
1999-03-27 20:44                 ` David Edelsohn
1999-04-02 12:11             ` Holger Bettag
1999-04-02 17:11               ` David Edelsohn
1999-04-02 22:19                 ` Douglas Godfrey
1999-04-03 17:42                 ` Holger Bettag
1999-04-05 16:11                   ` Gabriel Paubert
1999-04-05 16:06               ` Gabriel Paubert
1999-04-06  5:53                 ` Douglas Godfrey
1999-03-26  6:08         ` Nathan Hurst
1999-03-26 13:51           ` sean o'malley
1999-03-28  5:08             ` Cort Dougan
1999-03-26 20:33           ` N.G. Temme
1999-03-29 23:44       ` Blue G3 and machine check Paul Mackerras
1999-03-30 11:41         ` Gabriel Paubert
1999-03-31 16:20           ` Ryuichi Oikawa
1999-03-31 18:39             ` Gabriel Paubert
1999-04-05 16:36               ` Ryuichi Oikawa
1999-04-05 17:11                 ` Gabriel Paubert
1999-04-04  1:17             ` Joel Klecker
1999-04-09  5:58               ` Joel Klecker
1999-04-09 16:12                 ` Ryuichi Oikawa [this message]
1999-03-25 12:10     ` Benjamin Herrenschmidt

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=19990410011237E.roikawa@rr.iij4u.or.jp \
    --to=roikawa@rr.iij4u.or.jp \
    --cc=jk@espy.org \
    --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).