From: Ralf Baechle <ralf@linux-mips.org>
To: sknauert@wesleyan.edu
Cc: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>,
linux-mips@linux-mips.org
Subject: Re: SGI O2 meth: missing sysfs device symlink
Date: Tue, 22 May 2007 13:28:08 +0100 [thread overview]
Message-ID: <20070522122808.GD32557@linux-mips.org> (raw)
In-Reply-To: <34888.129.133.92.31.1179835313.squirrel@webmail.wesleyan.edu>
On Tue, May 22, 2007 at 08:01:53AM -0400, sknauert@wesleyan.edu wrote:
> I've noticed that besides kernel complied from the Debian 2.6.18, I can't
> get any other kernel (vanilla from kernel.org or the separate linux-MIPS
> repository) to boot on my O2.
>
> If you need beta testers, I can try, but it will take a day or so
> (compiling on the O2 is slow).
Sounds almost like you're building an excessibly large kernel configuration.
A realistic kernel config will crosscompile within a few minutes on a
modest machine such as a 3GHz / 1GB P4-class PC.
But to lessen the pains of your aching CPU, here's a binary tarball:
ftp://ftp.linux-mips.org/pub/linux/mips/people/ralf/sgi-ip32/linux-2.6.22-rc2-gc6b5a619-dirty.tar.bz2
> Finally, I've been working on the PCI Legacy IO issue (progress is sadly
> slow - don't have a fully compiling patchset yet), would this patch be
> relevant since its also an O2 sysfs issue?
The two issues are entirely unrelated.
Ralf
next prev parent reply other threads:[~2007-05-22 12:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1178743456.15447.41.camel@scarafaggio>
[not found] ` <20070516151939.GH19816@deprecation.cyrius.com>
[not found] ` <20070516160313.GA3409@bongo.bofh.it>
[not found] ` <50621.192.168.2.50.1179383217.squirrel@eppesuigoccas.homedns.org>
2007-05-17 15:16 ` SGI O2 meth: missing sysfs device symlink Martin Michlmayr
2007-05-21 15:47 ` Ralf Baechle
2007-05-22 11:09 ` Ralf Baechle
2007-05-22 11:41 ` Giuseppe Sacco
2007-05-22 12:01 ` sknauert
2007-05-22 12:28 ` Ralf Baechle [this message]
2007-05-22 13:32 ` sknauert
2007-05-22 15:18 ` Thiemo Seufer
2007-05-22 16:46 ` Cross-Compile difficulties sknauert
2007-05-22 17:32 ` Geert Uytterhoeven
2007-05-22 22:44 ` sknauert
2007-05-22 23:26 ` Carlos Munoz
2007-05-23 3:42 ` Kumba
2007-05-23 17:41 ` sknauert
2007-05-23 6:12 ` Geert Uytterhoeven
2007-05-22 13:02 ` SGI O2 meth: missing sysfs device symlink Thiemo Seufer
2007-05-22 12:13 ` Giuseppe Sacco
2007-05-22 13:00 ` Ralf Baechle
2007-05-23 11:45 ` Giuseppe Sacco
2007-05-24 11:47 ` Ralf Baechle
2007-05-23 3:51 ` Kumba
2007-05-23 8:37 ` Ralf Baechle
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=20070522122808.GD32557@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-mips@linux-mips.org \
--cc=sknauert@wesleyan.edu \
/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