From: Rudolf Usselmann <rudi@asics.ws>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
"Frank Denis (Jedi/Sector One)" <j@pureftpd.org>,
linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: kernel (64bit) 4GB memory support
Date: Wed, 11 May 2005 12:02:55 +0700 [thread overview]
Message-ID: <1115787775.4412.58.camel@cpu10> (raw)
In-Reply-To: <1115755412.14061.12.camel@mindpipe>
On Tue, 2005-05-10 at 16:03 -0400, Lee Revell wrote:
> On Wed, 2005-05-11 at 02:48 +0700, Rudolf Usselmann wrote:
> > All my problems started when I "upgraded" to x86_64 ...
> >
>
> And you are surprised by this?
>
> I don't know why so many users buy an arch that didn't exist two years
> ago and expect it to be 100% as reliable as 32 bit i386 which has been
> around for 20 plus years. I see tons of bug reports where people don't
> bother to mention that "oh, btw this is a mixed 32/64 bit environment"
> or whatever.
>
> When you make the choice to live on the bleeding edge, these things will
> happen. If you don't like filling out bug reports stick with a 32 bit
> machine ;-)
>
> Lee
Hi Lee,
no I am not surprised ! But, hey, if nobody tries, we will
never debug it, right ?! ;*)
I did fill out a bug report several month ago (and did not mind
it), I was just following up because I didn't hear anything about
it in quite sometime !
Best Regards,
rudi
=============================================================
Rudolf Usselmann, ASICS World Services, http://www.asics.ws
Your Partner for IP Cores, Design, Verification and Synthesis
next prev parent reply other threads:[~2005-05-11 5:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 8:16 kernel (64bit) 4GB memory support Rudolf Usselmann
2004-12-11 10:06 ` Jeff Garzik
2004-12-11 10:13 ` Rudolf Usselmann
2004-12-11 11:22 ` Andrew Walrond
2004-12-11 17:47 ` Jeff Garzik
2004-12-12 4:12 ` Rudolf Usselmann
2004-12-12 4:41 ` Zwane Mwaikambo
2004-12-12 5:10 ` Rudolf Usselmann
2004-12-12 8:32 ` Zwane Mwaikambo
2004-12-12 9:15 ` Rudolf Usselmann
2004-12-12 16:35 ` Zwane Mwaikambo
2004-12-14 12:25 ` Rudolf Usselmann
2004-12-15 4:22 ` Zwane Mwaikambo
[not found] ` <20041216074905.GA2417@c9x.org>
2004-12-16 16:09 ` Rudolf Usselmann
2004-12-20 19:49 ` Zwane Mwaikambo
2004-12-21 16:23 ` Rudolf Usselmann
2004-12-21 16:33 ` Zwane Mwaikambo
2004-12-21 16:39 ` Rudolf Usselmann
2004-12-21 16:56 ` Zwane Mwaikambo
2005-05-09 15:56 ` Rudolf Usselmann
2005-05-09 20:07 ` Lennart Sorensen
2005-05-10 19:48 ` Rudolf Usselmann
2005-05-10 20:03 ` Lee Revell
2005-05-11 5:02 ` Rudolf Usselmann [this message]
2005-05-10 22:58 ` Terry Vernon
2005-05-12 3:53 ` Stefan Smietanowski
2005-05-11 14:27 ` Lennart Sorensen
2005-05-12 3:56 ` Stefan Smietanowski
2005-05-12 4:04 ` Rudolf Usselmann
2005-05-12 15:13 ` William Lee Irwin III
2005-05-09 20:07 ` Andi Kleen
2005-05-09 22:24 ` Zwane Mwaikambo
2005-05-10 19:50 ` Rudolf Usselmann
2005-05-09 23:13 ` kernel (64bit) 4GB memory support II Andi Kleen
2005-01-13 17:26 ` kernel (64bit) 4GB memory support Rudolf Usselmann
2005-01-14 23:34 ` Zwane Mwaikambo
2005-01-15 5:34 ` Rudolf Usselmann
2005-01-17 4:54 ` Zwane Mwaikambo
2004-12-11 11:35 ` bert hubert
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=1115787775.4412.58.camel@cpu10 \
--to=rudi@asics.ws \
--cc=j@pureftpd.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=rlrevell@joe-job.com \
--cc=zwane@arm.linux.org.uk \
/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.