From: Indrek Kruusa <indrek.kruusa@artecdesign.ee>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: long/heavy USB fs operations panics 2.6.16.18
Date: Wed, 31 May 2006 11:20:24 +0300 [thread overview]
Message-ID: <447D51C8.8040503@artecdesign.ee> (raw)
In-Reply-To: <20060530031037.GA11543@cosmic.amd.com>
Jordan Crouse wrote:
> On 29/05/06 19:41 +0300, Indrek Kruusa wrote:
>
>> Duh... I have to doublecheck it but currently it seems that our BIOS
>> needs a fix. I hope you haven't had much trouble with my problem report.
>> I much appreciate your feedback.
>>
>
> Well, let us know if the problem persists. Good luck.
>
I am not able to describe it in depth but there was "layout" or
"placement" changes needed in our mini-version BIOS (so they said). I
just figured out that with full-blown BIOS there wasn't problems. By now
the "mini" BIOS is also OK (especially for Linux).
Indrek
prev parent reply other threads:[~2006-05-31 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 17:20 [GeodeLX] long/heavy USB fs operations panics 2.6.16.18 Indrek Kruusa
2006-05-24 19:25 ` Jordan Crouse
2006-05-26 7:48 ` Indrek Kruusa
2006-05-26 13:38 ` Indrek Kruusa
2006-05-29 16:41 ` Indrek Kruusa
2006-05-30 3:10 ` Jordan Crouse
2006-05-31 8:20 ` Indrek Kruusa [this message]
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=447D51C8.8040503@artecdesign.ee \
--to=indrek.kruusa@artecdesign.ee \
--cc=jordan.crouse@amd.com \
--cc=linux-kernel@vger.kernel.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