Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Jerry <jerry@wicomtechnologies.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	linux-mips <linux-mips@linux-mips.org>
Subject: Re: 64 bit kernel for BCM1250
Date: Mon, 23 May 2005 08:39:21 -0700	[thread overview]
Message-ID: <4291F929.9000302@avtrex.com> (raw)
In-Reply-To: <27582192.20050523182609@wicomtechnologies.com>

Jerry wrote:
> Hello Maciej,
> Thursday, May 19, 2005, 6:19:14 PM, you wrote:
> 
> 
>> For 64-bit builds you probably want to use fairly recent versions or you
>>risk hitting serious bugs that used to exist in older versions.  Using
>>David's patch (or preferably mine ;-) -- as available here: 
>>"http://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-mips&i=Pine.LNX.4.55.0406281509170.23162%40jurand.ds.pg.gda.pl";
>>which I keep using with GCC 4.0.0) is probably the lesser evil.
> 
> 
>  Without going into details - what difference between your and David's
> patch ? :) I'm in doubts which one is more suitable for me...
> 

FWIW: My current patch is quite similar to Maciej's.

David Daney.

  reply	other threads:[~2005-05-23 15:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 13:52 64 bit kernel for BCM1250 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 [this message]
  -- 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-18  8:09 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-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=4291F929.9000302@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=jerry@wicomtechnologies.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@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