LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: "Rik van Riel" <riel@redhat.com>,
	"Christian Kujau" <lists@nerdbynature.de>,
	"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 64-bit AMD panic
Date: Tue, 4 Mar 2008 01:11:41 +0100	[thread overview]
Message-ID: <9a8748490803031611m4ad2cd7dr16e30e7cb003c05f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0803031704290.7011@chaos.analogic.com>

On 03/03/2008, linux-os (Dick Johnson) <linux-os@analogic.com> wrote:
>
<snip>
>
> That's the problem trying to support devices in production.
>  The last kernel I was able to locate for the x86_64 project
>  is linux-2.6.23. Its dates are from late last year so maybe
>  it will work!
>
>  It is now being compiled one one of the target machines.
>  If this works, I'll have to find the differences between
>  the old and the newer and patch the linux-2.6.11 because
>  it is a "certified" kernel, i.e., selected by the FAA and
>  determined to be politically correct!

So, you take a "certified" kernel, then you patch it, which leaves you
with what? Certainly not a certified kernel. You might as well go with
the latest 2.6.24.3 sources then...

>
<snip>
>

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  parent reply	other threads:[~2008-03-04  0:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 17:06 linux-os (Dick Johnson)
2008-03-03 18:45 ` Christian Kujau
2008-03-03 21:22   ` Rik van Riel
2008-03-03 22:10     ` linux-os (Dick Johnson)
2008-03-03 22:21       ` Rik van Riel
2008-03-04  0:11       ` Jesper Juhl [this message]
2008-03-04 14:21         ` linux-os (Dick Johnson)
2008-03-06 16:41 ` Chris Snook

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=9a8748490803031611m4ad2cd7dr16e30e7cb003c05f@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=lists@nerdbynature.de \
    --cc=riel@redhat.com \
    --subject='Re: 64-bit AMD panic' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).