From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: linux 2.4 and Indy
Date: Thu, 29 Jan 2004 05:40:34 -0500 [thread overview]
Message-ID: <4018E322.9030801@gentoo.org> (raw)
In-Reply-To: <20040129102215.GC17760@ballina>
Jorik Jonker wrote:
> Hi,
>
> I'm having big trouble getting linux 2.4.* to work on my SGI Indy. I want to
> use my indycam, and thus compile a kernel with support for that. The problem
> is that all the kernels I built do boot, but freeze some moments after
> starting the init process. The only kernels that do not have this problem are
> 2.4.16 and 2.4.17, but they do not have proper VINO support (they lack the
> i2c algo-sgi part).
> Is there some patch flying around to fix this, or do I just have bad luck?
Check out a cvs tree no later than 12/11/2003, a change in CVS after
that date seems to have nuked r4k kernels. It is believed the change in
question is:
http://www.linux-mips.org/archives/linux-cvs/2003-12/msg00031.html
I've not yet been able to find a 'clean' way to remove the changes to
those specific files in that commit while keeping all the changes made
afterwards intact to test this idea.
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world:
small hands do them because they must, while the eyes of the great are
elsewhere." --Elrond
next prev parent reply other threads:[~2004-01-29 10:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 10:22 linux 2.4 and Indy Jorik Jonker
2004-01-29 10:40 ` Kumba [this message]
2004-01-30 10:59 ` Jorik Jonker
2004-01-30 11:12 ` Dominik 'Rathann' Mierzejewski
2004-01-30 20:49 ` Jorik Jonker
2004-01-30 21:01 ` Jorik Jonker
2004-01-31 3:04 ` Ralf Baechle
2004-01-31 14:10 ` Jorik Jonker
2004-02-01 4:52 ` R4600 V1.7 errata Ralf Baechle
2004-02-03 11:39 ` Ralf Baechle
2004-02-03 11:42 ` Dominik 'Rathann' Mierzejewski
2004-02-03 11:52 ` Ralf Baechle
2004-02-03 15:43 ` Maciej W. Rozycki
2004-02-03 16:12 ` Ralf Baechle
2004-02-03 16:20 ` Maciej W. Rozycki
2004-02-04 15:48 ` Dominik 'Rathann' Mierzejewski
2004-02-04 15:59 ` Pete Popov
2004-02-04 20:04 ` 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=4018E322.9030801@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.