Arjan van de Ven, Mon, Jul 02, 2007 19:18:29 +0200:
> On Mon, 2007-07-02 at 10:56 +0200, Alex Riesen wrote:
> > On 3/23/07, Shaohua Li <[EMAIL PROTECTED]> wrote:
> > > On Thu, 2007-03-22 at 23:45 +, Daniel J Blueman wrote:
> > > > Is the tool you mentioned last June [1] available for splitting
On Mon, 2007-07-02 at 10:56 +0200, Alex Riesen wrote:
> On 3/23/07, Shaohua Li <[EMAIL PROTECTED]> wrote:
> > On Thu, 2007-03-22 at 23:45 +, Daniel J Blueman wrote:
> > > Is the tool you mentioned last June [1] available for splitting up the
> > > old firmware files to the new format (eg
> > >
On 3/23/07, Shaohua Li <[EMAIL PROTECTED]> wrote:
On Thu, 2007-03-22 at 23:45 +, Daniel J Blueman wrote:
> Is the tool you mentioned last June [1] available for splitting up the
> old firmware files to the new format (eg
> /lib/firmware/intel-ucode/06-0d-06), or are updates available from
> I
> I was mainly concerned with this being a new issue, and curious if
> Microsoft was calling an O/S bug a "microcode fix," given that the
> average Windows user doesn't know microcode from nanotech anyway. The
> non-answer from Arjan didn't answer either, and started by calling the
> report FUD
Chuck Ebbert wrote:
On 06/28/2007 11:27 AM, Andi Kleen wrote:
But the problem is very obscure and you can likely ignore it too. If your
machine crashes it's very likely something else.
What about deliberate exploits of these bugs from userspace? Theo thinks
they are possible...
Do you have an
> I was mainly concerned with this being a new issue, and curious if
> Microsoft was calling an O/S bug a "microcode fix," given that the
> average Windows user doesn't know microcode from nanotech anyway. The
> non-answer from Arjan didn't answer either, and started by calling the
then ask qu
Andi Kleen wrote:
Slashdot carried an article this morning saying that an error in Intel
microcode was being fixed. However, it listed only Windows related sites
That's a little misleading. Always dangerous getting your information
from slashdot. Let's say Intel clarified some corner
cas
On 28/06/07, Chuck Ebbert <[EMAIL PROTECTED]> wrote:
On 06/28/2007 10:12 AM, Arjan van de Ven wrote:
[snip]
>> However, it listed only Windows related sites
>> for the "fix" download. Is this the same TLB issue? And are these really
>> fixes for Windows to flush the TLB properly the way Linux
Chuck Ebbert wrote:
On 06/28/2007 10:12 AM, Arjan van de Ven wrote:
(while I work for Intel this is not an official Intel statement, but
there is so much FUD going around now that I feel I need to at least
point out a few things others "forget")
Slashdot carried an article this morning saying th
On 06/28/2007 10:12 AM, Arjan van de Ven wrote:
> (while I work for Intel this is not an official Intel statement, but
> there is so much FUD going around now that I feel I need to at least
> point out a few things others "forget")
>> Slashdot carried an article this morning saying that an error in
By any chance, do you known anything about microcode driver which
uses standard firmware load interfaces (like those used by wlan card)?
In particular, what format does the driver expect the microcode in?
It didn't accept Tigran's files in past, does it accept them now?
-
To unsubscribe from this
On 06/28/2007 11:27 AM, Andi Kleen wrote:
>
> But the problem is very obscure and you can likely ignore it too. If your
> machine crashes it's very likely something else.
What about deliberate exploits of these bugs from userspace? Theo thinks
they are possible...
-
To unsubscribe from this lis
> Slashdot carried an article this morning saying that an error in Intel
> microcode was being fixed. However, it listed only Windows related sites
That's a little misleading. Always dangerous getting your information
from slashdot. Let's say Intel clarified some corner
cases in TLB flushing th
(while I work for Intel this is not an official Intel statement, but
there is so much FUD going around now that I feel I need to at least
point out a few things others "forget")
> >
> Slashdot carried an article this morning saying that an error in Intel
> microcode was being fixed.
don't just a
Andi Kleen wrote:
"Daniel J Blueman" <[EMAIL PROTECTED]> writes:
On 23/03/07, Shaohua Li <[EMAIL PROTECTED]> wrote:
On Thu, 2007-03-22 at 23:45 +, Daniel J Blueman wrote:
Hi Shao-hua,
Is the tool you mentioned last June [1] available for splitting up the
old firmware files to the new for
"Daniel J Blueman" <[EMAIL PROTECTED]> writes:
> On 23/03/07, Shaohua Li <[EMAIL PROTECTED]> wrote:
> > On Thu, 2007-03-22 at 23:45 +, Daniel J Blueman wrote:
> > > Hi Shao-hua,
> > >
> > > Is the tool you mentioned last June [1] available for splitting up the
> > > old firmware files to the n
On 23/03/07, Shaohua Li <[EMAIL PROTECTED]> wrote:
On Thu, 2007-03-22 at 23:45 +, Daniel J Blueman wrote:
> Hi Shao-hua,
>
> Is the tool you mentioned last June [1] available for splitting up the
> old firmware files to the new format (eg
> /lib/firmware/intel-ucode/06-0d-06), or are updates
Marcel Holtmann wrote:
that is the whole point. The slash was never meant to be used. It was
designed to take a filename or a pattern that will be later matched by
userspace. However some developers are now trying to abuse this since
the simple firmware helper script matches this directly to a fi
Hi Arjan,
> > > > Is the tool you mentioned last June [1] available for splitting up the
> > > > old firmware files to the new format (eg
> > > > /lib/firmware/intel-ucode/06-0d-06), or are updates available from
> > > > Intel (or otherwise) in this new format?
> > > Yes, we are preparing the new
On Fri, 2007-03-23 at 10:43 +0100, Marcel Holtmann wrote:
> Hi Li,
>
> > > Is the tool you mentioned last June [1] available for splitting up the
> > > old firmware files to the new format (eg
> > > /lib/firmware/intel-ucode/06-0d-06), or are updates available from
> > > Intel (or otherwise) in th
Hi Li,
> > Is the tool you mentioned last June [1] available for splitting up the
> > old firmware files to the new format (eg
> > /lib/firmware/intel-ucode/06-0d-06), or are updates available from
> > Intel (or otherwise) in this new format?
> Yes, we are preparing the new format data files and m
On Thu, 2007-03-22 at 23:45 +, Daniel J Blueman wrote:
> Hi Shao-hua,
>
> Is the tool you mentioned last June [1] available for splitting up the
> old firmware files to the new format (eg
> /lib/firmware/intel-ucode/06-0d-06), or are updates available from
> Intel (or otherwise) in this new fo
Hi Shao-hua,
Is the tool you mentioned last June [1] available for splitting up the
old firmware files to the new format (eg
/lib/firmware/intel-ucode/06-0d-06), or are updates available from
Intel (or otherwise) in this new format?
Thanks,
Dan
--- [1]
http://lwn.net/Articles/189377/
--
Danie
23 matches
Mail list logo
