It looks like the version in the tree is actually already fixed.
Execution is now getting to the point where the wbinvd instruction is
being executed. This instruction is supposed to write back the contents
of the cache and mark everything invalid, and from previous
conversations I know there
On Dec 24, 2008, at 2:55 AM, Gabe Black wrote:
It looks like the version in the tree is actually already fixed.
Execution is now getting to the point where the wbinvd instruction is
being executed. This instruction is supposed to write back the
contents
of the cache and mark everything
I recently put the mkblankimage.sh script in m5/util. My guess is
that we should remove the one from the website (with maybe a pointer
to the repository) and fix the one in the tree. Can you take care of
it gabe?
I have the M5 ops working, but the slow IDE controller turned out to be
a bug in
Yes. I'm having network issues so it might not make it into the tree quickly.
Gabe
Quoting nathan binkert n...@binkert.org:
I recently put the mkblankimage.sh script in m5/util. My guess is
that we should remove the one from the website (with maybe a pointer
to the repository) and fix the
nathan binkert wrote:
I notice there's a copy of the m5 op stuff in both the main repository
and in the kernel patches, and that the version in the kernel patches
isn't the same. Should they be? Do I need to link them together somehow?
The version in the main repository has some definitions
, December 19, 2008 3:50 AM
To: M5 Developer List
Subject: [m5-dev] SLOOW IDE controller
I finally have the IDE controller sort of working (yay!), but
apparently there's a built in 3 millisecond busy loop delay before
the
device is recognized as ready to go. In general, did you need to do
I notice there's a copy of the m5 op stuff in both the main repository
and in the kernel patches, and that the version in the kernel patches
isn't the same. Should they be? Do I need to link them together somehow?
The version in the main repository has some definitions for functions
the other
I finally have the IDE controller sort of working (yay!), but
apparently there's a built in 3 millisecond busy loop delay before the
device is recognized as ready to go. In general, did you need to do
anything special to make the controller start up and work in a
reasonable amount of real
Black
Sent: Friday, December 19, 2008 3:50 AM
To: M5 Developer List
Subject: [m5-dev] SLOOW IDE controller
I finally have the IDE controller sort of working (yay!), but
apparently there's a built in 3 millisecond busy loop delay before the
device is recognized as ready to go. In general
] On
Behalf
Of Gabe Black
Sent: Friday, December 19, 2008 3:50 AM
To: M5 Developer List
Subject: [m5-dev] SLOOW IDE controller
I finally have the IDE controller sort of working (yay!), but
apparently there's a built in 3 millisecond busy loop delay before the
device
: Friday, December 19, 2008 3:50 AM
To: M5 Developer List
Subject: [m5-dev] SLOOW IDE controller
I finally have the IDE controller sort of working (yay!), but
apparently there's a built in 3 millisecond busy loop delay before the
device is recognized as ready to go. In general, did you
Developer List
Subject: [m5-dev] SLOOW IDE controller
I finally have the IDE controller sort of working (yay!), but
apparently there's a built in 3 millisecond busy loop delay before
the
device is recognized as ready to go. In general, did you need to do
anything special to make
...@m5sim.org] On
Behalf
Of Gabe Black
Sent: Friday, December 19, 2008 3:50 AM
To: M5 Developer List
Subject: [m5-dev] SLOOW IDE controller
I finally have the IDE controller sort of working (yay!), but
apparently there's a built in 3 millisecond busy loop delay before
the
device
...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On
Behalf
Of Gabe Black
Sent: Friday, December 19, 2008 3:50 AM
To: M5 Developer List
Subject: [m5-dev] SLOOW IDE controller
I finally have the IDE controller sort of working (yay!), but
apparently there's a built in 3 millisecond busy
14 matches
Mail list logo
