From: Jerry <jerry@wicomtechnologies.com>
To: David Daney <ddaney@avtrex.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re[2]: 64 bit kernel for BCM1250
Date: Mon, 23 May 2005 18:08:19 +0300 [thread overview]
Message-ID: <1371154543.20050523180819@wicomtechnologies.com> (raw)
In-Reply-To: <428B6EDD.4040508@avtrex.com>
Hello David,
Wednesday, May 18, 2005, 7:35:41 PM, you wrote:
>>>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.
>> That could actually be true -- I've been using GCC 4.0.0 for quite
>> some time now (that includes CVS snapshots from before the
>> release), so I have no slightest idea whether it's OK to use older
>> versions. ;-)
>>>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
>> Hasn't one of the proposed fixes for the bug made its way to Linux
>> in the end? That would be regrettable...
> WRT the 2.4 kernel the answer seems to be no. And yes I think it is
> regrettable. If anybody thinks it would be useful, I could post my
> current patch again.
Hmm right now I see the same result with oops caused
new_inode(pipe_mnt->mnt_sb) where pipe_mnt=0 witn 2.4 kernels and
gcc3.4.3 on dbau1200. If there was any changes in patch since Dec2004,
and if it hepls to solve this problem - can you please repost it
again?
()_()
-( ^,^ )- -[21398845]- -<The Bat! 3.0.1.33>- -<23/05/2005 18:03>-
(") (")
next prev parent reply other threads:[~2005-05-23 15:07 UTC|newest]
Thread overview: 6+ 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
2005-05-18 16:24 ` Maciej W. Rozycki
2005-05-18 16:35 ` David Daney
2005-05-23 15:08 ` Jerry [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-19 13:52 Michael Belamina
2005-05-19 15:19 ` Maciej W. Rozycki
2005-05-23 15:26 ` Re[2]: " Jerry
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=1371154543.20050523180819@wicomtechnologies.com \
--to=jerry@wicomtechnologies.com \
--cc=ddaney@avtrex.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