LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "linux-os (Dick Johnson)" <linux-os@analogic.com>
To: "Jesper Juhl" <jesper.juhl@gmail.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 09:21:15 -0500	[thread overview]
Message-ID: <Pine.LNX.4.61.0803040909100.10064@chaos.analogic.com> (raw)
In-Reply-To: <9a8748490803031611m4ad2cd7dr16e30e7cb003c05f@mail.gmail.com>


On Mon, 3 Mar 2008, Jesper Juhl wrote:

> 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>
>>

You are preaching to the choir. When doing government things
we can't resort to logic, only "rules!" Here's an example
of why; We decide to use the latest kernel which, BTW, we are
not allowed to decide that ourselves, we would have to obtain
a consensus from lots of "interested" people, including the
people who move equipment into place (will a later kernel
weigh more? ..They need to know). The process of selecting
a new kernel could take a year. Then, it needs to be
re-certified, which could cause a few million dollars (I am
not kidding...there are people who, working out of their
YMCA rooms, charge the government $600 / hour for such
code-reviews, etc).

That's why we almost always try for a "permissive" change.
In this case, after verifying that the USB works on a
later kernel (it does), I need to find out what changes
were made to make it work and I need to incorporate those
changes into the older driver.

Adding insult to injury, I find that the driver was not
changed much, but the memory allocation scheme for bounce
buffers. To review this stuff takes a lot of nights and
weekends because nobody will give me a hint of the changes
made to make USB work. It's not in any "Changes"
documentation, but somebody knows --and they aren't
telling!


Cheers,
Dick Johnson
Penguin : Linux version 2.6.22.1 on an i686 machine (5588.28 BogoMips).
My book : http://www.AbominableFirebug.com/
_


****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

  reply	other threads:[~2008-03-04 14:24 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
2008-03-04 14:21         ` linux-os (Dick Johnson) [this message]
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=Pine.LNX.4.61.0803040909100.10064@chaos.analogic.com \
    --to=linux-os@analogic.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).