From: David Daney <ddaney@avtrex.com>
To: Michael Belamina <belamina1@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: 64 bit kernel for BCM1250
Date: Wed, 18 May 2005 08:58:52 -0700 [thread overview]
Message-ID: <428B663C.7050308@avtrex.com> (raw)
In-Reply-To: <20050518080917.45521.qmail@web32501.mail.mud.yahoo.com>
Michael Belamina wrote:
.
.
.
> Linux version 2.4.30 (michael@LinuxServer.lan) (gcc
> version 3.4.3) #29 SMP Wed May 18 10:37:00 IDT 2005
.
.
.
>
> The fault is in do_pipe() function when trying to
> call:
>
> struct inode *inode = new_inode(pipe_mnt->mnt_sb);
>
> The pipe_mnt is NULL at this point because
> init_pipe_fs () was not called yet.
>
>
> Any ideas what could be wrong?
>
I saw this with a 32 bit kernel (for a 32 bit target). As far as I
know, no 2.4.x kernels from linux-mips.org will work with gcc 3.4.x.
I have previously posted patches to this list that fixed the problem for
me. Specifically I think the messages in this thread are relevant:
http://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-mips&i=41AFDA18.2010906%40avtrex.com
David Daney.
next prev parent reply other threads:[~2005-05-18 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 8:09 64 bit kernel for BCM1250 Michael Belamina
2005-05-18 15:58 ` David Daney [this message]
2005-05-18 16:24 ` Maciej W. Rozycki
2005-05-18 16:35 ` David Daney
2005-05-23 15:08 ` Re[2]: " Jerry
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 18:59 Michael Belamina
2005-05-31 14:57 ` Maciej W. Rozycki
2005-05-22 20:31 Michael Belamina
2005-05-19 13:52 Michael Belamina
2005-05-19 15:19 ` Maciej W. Rozycki
2005-05-23 15:26 ` Re[2]: " Jerry
2005-05-23 15:39 ` David Daney
2005-05-17 19:52 Michael Belamina
2005-05-17 9:36 Michael Belamina
2005-05-17 10:49 ` Maciej W. Rozycki
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=428B663C.7050308@avtrex.com \
--to=ddaney@avtrex.com \
--cc=belamina1@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox