Array mapping to AXIS tdata

Assuming following structure defining an array of a 3 member struct:
typedef struct{
ap_fixed<8,8> R;
ap_fixed<8,8> G;
ap_fixed<8,8> B;
} RGBPix;
typedef struct{
RGBPix Pix[4];
} slv120;
slv120 testdata[N];
The memory structure in software test bench is as expected:
char* byte_pointer_to_testdata = testdata;
byte_pointer_to_testdata[0] => Pix[0].R
byte_pointer_to_testdata[0] => Pix[0].G
byte_pointer_to_testdata[0] => Pix[0].B
byte_pointer_to_testdata[0] => Pix[1].R
byte_pointer_to_testdata[0] => Pix[1].G
byte_pointer_to_testdata[N-1] => Pix[3].R
byte_pointer_to_testdata[N-1] => Pix[3].G
byte_pointer_to_testdata[N-1] => Pix[3].B
However, when I assign slv120 to AXIS tdata I observe (via chiposcope):
tdata(7 downto 0) => Pix[0].R
tdata(15 downto 8) => Pix[1].R
tdata(23 downto 16) => Pix[2].R
tdata(31 downto 24) => Pix[3].R
tdata(39 downto 32) => Pix[0].G
tdata(119 downto 112) => Pix[3].B
Is there any reason for this rearrangement? It currently prevent me from generating a fitting data structure to match AXIS video data format
(see http://www.xilinx.com/support/documentation/ip_documentation/v_vid_in_axi4s/v3_0/pg043_v_vid_in_axi4s.pdf page 14).
How can I force the arrangement to fit to the needed structure?
Thanks!
remark: the SW test above was done using ap_fixed<8,8> while real HW was evaluated with ap_fixed<10,10>,
HW cosim for any word width is correct.

Hi Hervé,
thank you for pointing to the UG section, indeed very powerful stuff!
By using it I will be able to structure my data according to fit any external requirement.
Attached is the test project where you can see that a (8 bit) data structure in SW memory
is different from the generated HDL port structure (as described in my first post here).
Looking at the HDL output I see that one part, the R member what is set to constant,
is mapped 4 times to the lower side of the slv120 vector followed by the variable part.
I do not understand this mapping, it prevent effective work as it forces the user to figure out
how the actual mapping is applied and to remap this to the required structure.
More critical, what if in further version of the tool this mapping schema changes ???
Any idea how I can avoid the extra work?
Thanks,
Ric.
d_o_TDATA &colon; OUT STD_LOGIC_VECTOR (95 downto 0);
d_o_TDATA <= OUTPUT_STREAM_1_data_reg;
-- OUTPUT_STREAM_1_data_reg assign process. --
OUTPUT_STREAM_1_data_reg_assign_proc : process(ap_clk)
begin
if (ap_clk'event and ap_clk = '1') then
if (ap_rst_n_inv = '1') then
OUTPUT_STREAM_1_data_reg(0) <= '0'; -- .data.Pix[0].R
OUTPUT_STREAM_1_data_reg(8) <= '0'; -- .data.Pix[1].R
OUTPUT_STREAM_1_data_reg(16) <= '0';-- .data.Pix[2].R
OUTPUT_STREAM_1_data_reg(24) <= '0';-- .data.Pix[3].R
OUTPUT_STREAM_1_data_reg(32) <= '0';-- .data.Pix[0].G
OUTPUT_STREAM_1_data_reg(33) <= '0';
OUTPUT_STREAM_1_data_reg(34) <= '0';
OUTPUT_STREAM_1_data_reg(94) <= '0';
OUTPUT_STREAM_1_data_reg(95) <= '0';

Similar Messages

Proxy to JDBC- Array mapping

Hi,
In my scenario Proxy to JDBC - synchronous call.
In the receiver side using JDBC adapter a stored procedure is invoked and that returns some values say... IndentNumber,EmployeeNumber and ResumeNumbers (Which is array type.), Status(which is again array) -- ResumeNumbers may have multiple resume numbers and status has status flag corresponding to each resume.
How do I go about this in XI mapping.
Please guide me on this.
Regards,
chem
Edited by: Chemmanz on Mar 15, 2008 3:39 PM

Hi,
For this you need to make the occurance of the proxy structure as 1...unbounded.
If the fields have to mapped then make the Unbouded occurance and map it as it is.
OR for mulitple records....
For e.g.
Your JDBC side structure will be as
<root>
<StatementName5>
<storedProcedureName action= EXECUTE>
<table>realStoredProcedureeName</table>
<param1 [isInput=true] [isOutput=true] type=SQLDatatype>IndentNumber</param1>
</storedProcedureName >
</StatementName5>
</root>
Here make the occurance of IndentNumber as Unbounded so you will get whole array.
Now On Proxy side make the related structure and try to map the any one internal field i.e. array to root node
i.e. if proxy structure is
<root>
<IndentNumber></IndentNumber>
</root>
Then map JDBC response field IndentNumber -
> Root
This will create the multiple records for proxy.
Then all fields map as one to one mapping
IndentNumber (JDBC)->splitByValue>IndentNumber (Proxy)
Thnaks
Swarup

Mapping Arrays indexing in Crystal Reports formulas and indexes

I just took a Crystal Reports Designer class today and I presented the Array Mapping technique to the instructor. Since he was very interested I decided to post it here, so more people can benefit from it. This is an idea used a lot in C++. I designed a formula using two symmetric arrays. One to hold values to be used to test a condition, and a second one to hold values to be outputted when the condition is found. Since the index in the test values array for a given value to be tested matches the index of return values array of the correspondent output value, this methodology is called index mapping. Here follows the code: //testValues array store values to be tested in the formulaLocal StringVar Array testValues := MakeArray ( "S", "M", "L", "XL"); //returnValues array store values to be returned by the test formulaLocal StringVar Array returnValues := MakeArray ( "Small", "Medial", "Large", "Extra Large", "App Type not Found");Local NumberVar i := 1;Local Numbervar returnIndex := -1; //Loop through the entire array for each values of the fieldWhile i <= Ubound(testValues) AND returnIndex = -1 Do(//Actual test of the values and return bellow If ToText({CUSTOMER.SIZE}, 0) = testValues Then( returnIndex := i;); i := i + 1;); //If any value found return it, else return last value in the return value arrayIf returnIndex = -1 Then returnValues[Ubound(testValues) + 1]Else returnValues[returnIndex] Fell free to email me if you have questions and enjoy the code...

Can you help with the below?
Group on Client/Location, Brokerage Rate, Product
Read all records for a particular group and store each different currency in an array
On change of group display contents of the stored array.
e.g.
Record 1 ABN AM FUTURE RATE AGREEMENT 0.012500% DKK
Record 2 ABN AM FUTURE RATE AGREEMENT 0.012500% EUR
Record 3 ABN AM FUTURE RATE AGREEMENT 0.012500% GBP
Record 4 ABN AM FUTURE RATE AGREEMENT 0.012500% USD
On change of group I would like to display the following
 ABN AM FUTURE RATE AGREEMENT 0.012500% DKK EUR GBP USD

Map in an Axis Camera

How to map an axis camera?

If the camera is on a local subnet (or plugged into your PC), it should show up in MAX. If it is in a remote subnet, it is much more difficult. We have not (yet) figured out how to make the LabVIEW tools "find" the camera (even when we know its IP) -- we end up having to create the iid (and the other file type, whose extension I've temporarily forgotten) files ourselves, then MAX can find them.

Arrays greater than 0 and taking only the elements that doesn't contain that

Hi, I have 6 arrays.
X-Axis, Y-Axis, PressRef, TempRef, PV, and VecorPress.
I have created a spreadsheet for them using txt
When I use colum 1 (X-Axis) Vs. column 2 (y-axis) to plot in an XY graph in excel, I want to delete all ELEMENTS that have the value ZERO on my X-axis.
Meaning that all the elements of X-axis that are 0's.
For example..
I have X,Y,Z
130     15   16
130   15   17
0         16   17
131   16   17
When I have it in my text. I only want to see this
130     15   16
130   15   17
131   16   17
I have a diagram picture of what i currently have and then i have a txt file that i currntly have. can someone help me?
thank you
Best regards,
Krispiekream
Attachments:
Image2.jpg ‏76 KB
New Text Document.txt ‏158 KB

The OpenG functions can be found from the OpenG site. They save you the trouble of having the code some stuff up yourself.
The "code it yourself approach" using a temporary 2D array looks like this:
Note: As I said, there will be some memory thrashing as LabVIEW allocates memory for the growing 2D array. The alternate method I described would use "Initialize Array" to create a 2D array and then use Replace Subset to "insert" the rows into the 2D array. I will leave it as a learning exercise for you to code that up.
Message Edited by smercurio_fc on 11-05-2007 05:15 PM
Attachments:
Example_BD.png ‏14 KB

3D bar graph with time stamp on X-axis

Hi all....I try to plot date data (first column in array) to x axis in 3D bar graph follow by example in this link
http://forums.ni.com/t5/LabVIEW/3D-bar-graph-issues-using-2D-Y-Z-plane-and-timestamp/td-p/1923027
But I still do not succeed.
I'll be glad if you had any suggestions that could help.
Thank you
HiN
Attachments:
xy_bar_graph Version 0.vi ‏21 KB

Hi Jubchay,
Here is an example of displaying the given timestamp. Only the 3D vision has the customized marker.
The 3D Bar is not suitable to display a lot of bars, which make the marker overlapped. So I only input the subset of 15.
Attachments:
xy_bar_graph Version 1.vi ‏23 KB

PCIe/AXI to user logic addressing

Hi,
I’m using a Spartan-6 XC6SLX45T-FGG484-2 FPGA and I’m using the Xilinx Platform Studio.
I want a PCIe host pc to communicate with two instances of a third party IP core via AXI4 memory mapped.
The host PC performs PCIe write and read transactions. The AXI slave responds to these transactions:
The AXI slave receives the data the host pc sent, and forwards it to the third party IP core, for a write request. For a read request, the AXI slave reads the data from the third party IP core, and sends it via AXI to the PCIe host pc.
My design looks like this:
PCIe/AXI MM bridge <> AXI Interconnect <> AXI_to_User_Logic <> 3rd_party_IP_core_0
<> 3rd_party_IP_core_1
AXI_to_User_Logic is an AXI4 memory mapped slave with two address spaces, that was created with the Create & Import Peripheral Wizard.
My first question is:
I think the PCIe/AXI bridge should be the AXI Master, so do I need to connect only the M_AXI to the AXI bus, or do I have to connect S_AXI and/or S_AXI_CTL as well?
The next question is: how to set the addresses?
I’m not sure whether I understood how to do the addressing, so I’d like someone to verify that the addressing I made is right. If it’s wrong, please show me how it has to be done.
I want to send 32 bytes to each AXI address space of the AXI slave and read 32 bytes from each AXI address space of the Slave.
Addresses of PCIe/AXI bridge IP core:
PCIe/AXI bridge: AXI Device Base Address (C_Baseaddr) = ?
PCIe/AXI bridge: AXI Device High Address (C_Highaddr) = ?
These Addresses can only be set in the PCIe/AXI bridge, not in the Slave. What do they mean? How should they be set?
Write and Read 32 Bytes to/from two AXI address spaces means: PCIe BAR size = 32 Bytes *2*2 = 128 Bytes (?).
128 = 2^7 --> PCIe BAR needs the lower 7 Bits to be 0 --> The bridge’s parameter C_PCIEBAR _LEN_0 = 7
The PCIe BAR gets determined by the configuration software.
Do I need an AXI BAR in the bridge? I don’t think so, as I only want to use the AXI Master Interface, right?
PCIe/AXI bridge: AXI Base Address 0 (C_AXIBAR_0) = ?
PCIe/AXI bridge: AXI High Address 0 (C_AXIBAR_HIGHADDR_0) = ?
PCIe BAR 0 mapped from AXI BAR 0 (C_AXIBAR2PCIEBAR_0) = ?
This BAR is only needed, if the endpoint (AXI/PCIe bridge) wants to initiate a transaction to the root port (that’s what I read about it, in the Xilinx support forum). So I don’t need this, right?
AXI BAR 0 mapped from PCIe BAR 0 (C_PCIEBAR2AXIBAR_0) = 0000 0000
Addresses of the User Logic IP core:
AXI_to_User_Logic_0:Mem0 Base Address = 0000 0000
AXI_to_User_Logic_0:Mem0 High Address = 0000 001F
AXI_to_User_Logic_0:Mem1 Base Address = 0000 0020
AXI_to_User_Logic_0:Mem1 High Address = 0000 003F
--> Both address spaces are 32 Bytes.
Let’s say the configuration software set the PCIe BAR0 to 0x0100 0000.
If the User_logic’s BARs and the PCIEBAR2AXIBARs are configured like above, I can access the second axi address space by performing a PCIe transaction with PCIe Baseaddress = 0100 0020 which will result in an AXI request with address = 0x00000020. Is this right?
I appreciate any help,
Fabian

interconnect is when you have one master, multiple slaves or multiple masters, single slave or any combination of NxM connectivity. If you have a single master and a single slave then there is no need for an interconnect and you can connect your master to the slave directly.
If you want a master example, you can do "tools|create&package ip|create new ip" and create an ip with master interface. Then you can add your master state machine/controller inside.
Also keep in mind that if you want your master to talk to your own slave and DDR you need to either have two master interface in your IP block or add an interconnect to demux your master to two separate slaves.

Selecting certain data from Array

Here is the issue I am faced with.
I am currently using an HTTPService call to a PHP document
that builds XML. I then take that XML and place it into an Array,
(pretty basic as you can tell.)
What I am dealing with is that I have 15 tabs that all
contain similar "notes" sections. I would really like to run 1
HttpService that returns all of the data form the notes, (note
data, username of note) and then placing the appropriate notes data
to the appropriate tab and data grid container.
So I didn't know if there was a way you could select only a
certain part of an Array and then populate a datagrid with that
particular data?
Almost like cutting pieces of a large array out and
displaying thos pieces on different tabs.
Any help is appreciated.

Array has many functions that you can use to do pretty much
anythin goyu eant on it,
filter () method
AS3 function filter(callback:Function, thisObject:* =
null):Array
Executes a test function on each item in the array and
constructs a new array for all items that return true for the
specified function. If an item returns false, it is not included in
the new array.
map () method
AS3 function map(callback:Function, thisObject:* =
null):Array
Executes a function on each item in an array, and constructs
a new array of items corresponding to the results of the function
on each item in the original array.
etc .. look up in API documents it has examples too :
http://livedocs.adobe.com/flex/3/langref/index.html

How to draw xy graph with multiple y axis input?

Hi,
I have problem in xy graph, the xy graph only can show 1 signal from the y axis input ( As you can see in the attachment )
Is it possible to draw xy graph with 2 Y input? Or maybe there are another type of graph that possible to do this?
Note: the x axis should be from an input too ( not versus time / sample ).
All answer and advice are welcomed.
Best regards,
Alvin Chandra
Solved!
Go to Solution.
Attachments:
Example.vi ‏139 KB

Are you asking for a second Y scale on the graph?
If so, right click on the existing scale, select "Duplicate Scale". This will create a second scale. You can then (if you wish), right click on the new scale a select "Swap Sides" to put it on the other side of the graph.
Are you asking about adding a second plot?
If so then you need to bundle your arrays of X and Y points into clusters and build those into an array:
The X-axis is always from an input on the XY Graph. You just need to change the axis title. Easiest way to do this is to double click on the axis title and type the new name.
Rob

Regarding String array

I have a input string in this format
1 Aviation Lamp 1 Nos 3700 3,7002 Lighting Arrester 1 Nos 1600' 1,6003 Aviataion Lamp Cable 31 Rmt ' 270 8,370
I can able to display the 3,700 1,600 8,370 these values i want to store in a String array for this i have written code in this way but unable to succeed
Code:
String sub="1 Aviation Lamp 1 Nos 3700 3,7002 Lighting Arrester 1 Nos 1600' 1,6003 Aviataion Lamp Cable 31 Rmt ' 270 8,370";
i=3;
Matcher tdata = Pattern.compile(("\\d*,\\d{3}"), Pattern.CASE_INSENSITIVE).matcher(sub);//Matching is performed using regular expression here
while (tdata.find()) {
for (int ij = 0; ij < i; ij++) {
table[ij] = tdata.group();
System.out.println(" Result "+tdata.group());//trying to load values in string array
System.out.println(" "+tdata.group());
for (int ik = 0; ik < 3; ik++) {
System.out.println(" output " + table[ik]);//Displaying only 8,370.
Any suggestions please welcome
Praveen

Hi Praveen
Matcher tdata = Pattern.compile(("\\d*,d{3}"), Pattern.CASE_INSENSITIVE).matcher(sub);
From above statement of your code, if u see u have Pattern Object which contain regular expression of
one digit followed by comma and exactly three digits.
Than your trying to match your string sub with the above regular expression so this wont match,
you can confirm by using method tdata.matches() , this method returns true if it matches false if it don't.
you can use the following code to make your stuff work
String sub = "1 Aviation Lamp 1 Nos 3700 3,7002 Lighting Arrester 1 Nos 1600' 1,6003 Aviataion Lamp"
+ "Cable 31 Rmt ' 270 8,370";
 String []SplitSub = sub.split("\\s");
 Pattern p = Pattern.compile("\\d,\\d{3,}", Pattern.CASE_INSENSITIVE);
 int ij =0;
 String table[] = new String[SplitSub.length];
 if(SplitSub.length > 1)
 for(int i =0; i < SplitSub.length ; i++)
 Matcher m = p.matcher(SplitSub);
 if(m.matches())
 table[ij++] = SplitSub[i].substring(0,5);
 System.out.println(" Result " + SplitSub[i].substring(0,5));

AXI slave connection of PCIe AXI bridge IP

Hi:
I'm creating a system with IPI which have Microblaze, DDR3 and PCIe interface.
When connecting the AXI PCIe bridge block, I got some problem.
Currently, I can access DDR3 through PCIe.
The path is Host PC ==> PCIe ==> AXI PCIe bridge ==> AXI interconnect ==> DDR3.
Now, I want to send data from Microblaze to Host PC as well, but don't know how to do it.
Tthe path I think should be : MicroBlaze ==> AXI interconnect ==> AXI PCIe bridge ==> PCIe ==> Host PC.
How should I connect the S_AXI_CTL and S_AXI port on AXI PCIe bridge?
Should S_AXI_CTL be connected? Is it also connected to M_AXI port of AXI interconnect?
Thanks a lot!
David

This setup looks a bit dangerous because you are mapping PCIe->AXI to address 0x00000000 which will inturn get decoded and go back out to PCIe land.
The M_AXI port from pcie probably only needs access to mig and maybe uart. The microblaze Data port address space looks correct. Any access from microblaze to address 0x00000000 will get decoded by the interconnect and passed to the S_AXI port on the pcie bridge. Then, the pcie bridge translates the axi address 0x00000000 to the PCIe address 0xFF000000.
I'm not a PCIe guru but I believe the software on the host will need to configure its pcie bridge in order to allow access to motherboard resources from the development board. On a linux host, the pcie driver would be responsible to map host memory or motherboard resources to be accessable from the development board.

Should I be using 2D arrays for this problem (or) how do I go about solving

An array is being used to represent an organizational hierarchy. This is done by using the array subscript to map to the employee-id and the value in each element to represent the employee-id of the supervisor of the employee.
For example the first element in the array maps to the supervisor of employee-id 1, the second element maps to the supervisor of employee id 2. The corresponding value for the top person in the organization is set to -1.
For example the following array ?
7 5 7 10 -1 7 5 2 2 5
translates to the following hierarchical structure -
? employee 5 is the top boss
? employees 2, 7, and 10 report to employee 5
? employees 8 and 9 report to employee 2
? employees 1, 3 and 6 report to employee 7
? employee 4 reports to employee 10
The following diagram represents the organization structure
5
+ --- 2
| + --- 8
| + --- 9
|
+ --- 7
| + --- 1
| + --- 3
| + --- 6
|
+ --- 10
+ --- 4
5 is at level 1 in the organization.
2, 7 and 10 are at level 2
1, 3, 4, 6, 8, 9 are at level 3
Given an array of size N (the employee-ids being 1 to N), write a program to find the number of people in level L, where the top person in the organization is at level 1.

Database is overkill!
heres your assignment
package myjava.demo;
class DemoLevel{
 class LevelData{
 int members[];
 int size = 0;
 int level = 0;
 public String toString() { return "Level: " + level + " Size: " + size;}
 LevelData getNextLevel(int data[],LevelData current){
 LevelData nextlevel = new LevelData();
 nextlevel.level = current.level + 1;
 nextlevel.members = new int[data.length];
 for(int i = 0; i< data.length;i = i + 1){
 if(data[i] != -1 && current.members[data[i]-1] != 0){ //data[i] indicates i's parent. this ask if its a member of current
 nextlevel.members[i] = data[i]-1; //store its parent. not needed in this algo. but better then true and false
 nextlevel.size = nextlevel.size + 1;
 }else{ nextlevel.members[i] = 0;}
 return nextlevel;
 LevelData getFirstLevel(int data[]){
 LevelData firstlevel = new LevelData();
 firstlevel.level = 1;
 firstlevel.members = new int [data.length];
 for(int i = 0; i < data.length;i = i + 1){
 if(data[i] == -1){
 firstlevel.members[i] = -1;
 firstlevel.size = firstlevel.size + 1;
 }else { firstlevel.members[i] = 0;}
 return firstlevel;
 void execute(){
 int data[] = { 7, 5, 7, 10, -1, 7, 5, 2, 2, 5};
 LevelData current = getFirstLevel(data);
 System.out.println(current);
 while(current.size != 0)
 current = getNextLevel(data,current);
 System.out.println(current);
public class Demo {
 public static void main(String[] args) {
 DemoLevel dl = new DemoLevel();
 dl.execute();

Array of generics (JLS seems too restrictive)

Hi everybody,
with some friends (in a lab) we currently develop a compiler generator
(a la SableCC i.e SLR, LR, LALR).
Because we start last june, we develop using jdk 1.5 and
generics. For me, i think it save us lot of time mainly because
Map<NonTerminal,Map<LRItem,Node>> is more readable
than Map :)
And this is my question : why CREATION of array of generics is unsafe ?
I don't understand why a code like below is tagged unsafe :
HashMap<State,Action>[] maps=new HashMap<State,Action>[5];
for(int i=0;i<map.length;i++)
maps=new HashMap<State,Action>();
For me, the fact that JLS forbids array of generics creation
is too restrictive, only cases where type parameter are lost
should be tagged as unsafe.
Example :
Object[] array=maps; // unsafe
Object o=map; // weird but unsafe because
// Object[] o=(Object[])(Object)maps; must be unsafeWhat do you think about this ?
R�mi Forax

The question is why :
Future<Double>[] futures=new
Future<Double>[10000];
is not allowed. It seems safe !First of all, it would not be safe. The example below would exhibit exactly the same vulnerabilities with this assignment as it would with any of the allowed ones. This is because both the declared type and the runtime type would still be the same.
It seems the current implementation is not able to detect (and warn about) the unsafety of the assignment above. That's why you're not allowed to use it: allowing it would provide a very false sense of type-safety
and why :
Object[] o=futures;
is not tagged unsafe.
It's unsafe because you can write :
Object[] o=futures;
o[0]=new Future<String>(); // for the example, let
says Future is a class
R�mi ForaxThis is probably done to avoid redundancy. As far as I can see, in all cases where this could be unsafe, you have been notified about the lack of safety already when you first assigned to futures.

Question about intensity graphs

Hi all Labview gurus and lovers,
I have a question to all of you. Last time I encountered with the interesting problem connecting to the building of the intensity graphs from the measurements. Suppose I have a matrix of numbers actually the voltages that I give to piezo motors. Afterwards I get some data from the measurement and I build some intensity graph from that data. And I want that every measurement will corresponding to voltage that I gave to the piezo motor. So I want to build the intensity graph as I dictate to the program to build it.
Example: I want to scan area ,some square from x=0.5;y=0.5 to x=-0.5;y=-0.5. and I did some algoritm that builds me some matrix of numbers depending on resolution of the picture; for instance if the resolution is 256, so the number of x will be 256 just like y=256 kinda 256 lines. Afterwards I say to the intensity graph that Xmax is 0.5 and Xmin is -0.5 just like Ymax=0.5 and Ymin =-0.5; also I deliver to him x and y offset and multliplier. So when I see how it builds my gaph I dont see that it starts from the [0.5 0.5] point as I want it. So my question is: how can I be sure that it will start from the point I want it to start? And how can I dictate to the graph to start to build the graph from the point I want? Because the problem happens when I want to zoom some area. When I zoom some area it gives me something different from what I expect to get.
thank you.

dimani4 wrote:
... also I deliver to him x and y offset and multliplier.
What is your definition of deliver? I don't understand.
All you need to set is the offset and multiplier to define the linear relation between array indices and axis values.
In your particular case you would set x0=0.5 and dx= -1/256 or similar (might need a small tweak)
In summary, x0,dx define the mapping of array indices to real values. These never change for a given set of data. Xmin,Xmax, etc define the visible area. These are modifiied during zooming and are purely cosmetic.
dimani4 wrote:
When I zoom some area it gives me something different from what I expect to get.
You should learn how to ask efficiently. Attach a small example with some typical data in a diagram constant. Tell us what you get and tell us what you expect to get! In the above sentence "different" is not sufficient as a description, since both sides of the equation are undefined!
LabVIEW Champion . Do more with less code and in less time .

How to find the max data transfer rate(disk speed) supported by mobo?

I plan on replacing my current HDD with a new and bigger HDD.
For this I need to know the max data transfer rate(disk speed) that my mobo will support. However, dmidecode is not telling me that. Am I missing something?
Here's dmidecode:
# dmidecode 2.11
SMBIOS 2.5 present.
80 structures occupying 2858 bytes.
Table at 0x000F0450.
Handle 0xDA00, DMI type 218, 101 bytes
OEM-specific Type
Header and Data:
DA 65 00 DA B2 00 17 4B 0E 38 00 00 80 00 80 01
00 02 80 02 80 01 00 00 A0 00 A0 01 00 58 00 58
00 01 00 59 00 59 00 01 00 75 01 75 01 01 00 76
01 76 01 01 00 05 80 05 80 01 00 D1 01 19 00 01
00 15 02 19 00 02 00 1B 00 19 00 03 00 19 00 19
00 00 00 4A 02 4A 02 01 00 0C 80 0C 80 01 00 FF
FF 00 00 00 00
Handle 0xDA01, DMI type 218, 35 bytes
OEM-specific Type
Header and Data:
DA 23 01 DA B2 00 17 4B 0E 38 00 10 F5 10 F5 00
00 11 F5 11 F5 00 00 12 F5 12 F5 00 00 FF FF 00
00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A17
Release Date: 04/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.0
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: OptiPlex 755
Version: Not Specified
UUID: 44454C4C-5900-1050-8033-C4C04F434731
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0200, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0PU052
Version:
Handle 0x0300, DMI type 3, 13 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Space-saving
Lock: Not Present
Version: Not Specified
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
Handle 0x0400, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: 76 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 23, Stepping 6
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Not Specified
Voltage: 0.0 V
External Clock: 1333 MHz
Max Speed: 5200 MHz
Current Speed: 2666 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x0700
L2 Cache Handle: 0x0701
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0700, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Data
Associativity: 8-way Set-associative
Handle 0x0701, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 6144 kB
Maximum Size: 6144 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: <OUT OF SPEC>
Handle 0x0800, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PARALLEL
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-25 female
Port Type: Parallel Port PS/2
Handle 0x0801, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SERIAL1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0802, DMI type 126, 9 bytes
Inactive
Handle 0x0803, DMI type 126, 9 bytes
Inactive
Handle 0x0804, DMI type 126, 9 bytes
Inactive
Handle 0x0805, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0806, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB2
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0807, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB3
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0808, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB4
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0809, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB5
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB6
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB7
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB8
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ENET
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x080E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MIC
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0810, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-IN
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0811, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HP-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0812, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MONITOR
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x090A, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT1
Type: x1 Proprietary
Current Usage: In Use
Length: Long
Characteristics:
PME signal is supported
Handle 0x0901, DMI type 126, 13 bytes
Inactive
Handle 0x0902, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT2
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 2
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0903, DMI type 126, 13 bytes
Inactive
Handle 0x0904, DMI type 126, 13 bytes
Inactive
Handle 0x0905, DMI type 126, 13 bytes
Inactive
Handle 0x0906, DMI type 126, 13 bytes
Inactive
Handle 0x0907, DMI type 126, 13 bytes
Inactive
Handle 0x0908, DMI type 126, 13 bytes
Inactive
Handle 0x0A00, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Disabled
Description: Intel Graphics Media Accelerator 950
Handle 0x0A02, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: Intel Gigabit Ethernet Controller
Handle 0x0A03, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Enabled
Description: Intel(R) High Definition Audio Controller
Handle 0x0B00, DMI type 11, 5 bytes
OEM Strings
String 1: www.dell.com
Handle 0x0D00, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0F00, DMI type 15, 29 bytes
System Event Log
Area Length: 2049 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFFF01000
Status: Valid, Not Full
Change Token: 0x00000018
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: System limit exceeded
Data Format 2: System management
Descriptor 3: Log area reset/cleared
Data Format 3: None
Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x1100, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_1
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: AD00000000000000
Handle 0x1101, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_3
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1102, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_2
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1103, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_4
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1300, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FDFFFFFF
Range Size: 4064 MB
Physical Array Handle: 0x1000
Partition Width: 1
Handle 0x1400, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1401, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1101
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1402, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1102
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1403, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1103
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1410, DMI type 126, 19 bytes
Inactive
Handle 0x1800, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Enabled
Keyboard Password Status: Not Implemented
Administrator Password Status: Enabled
Front Panel Reset Status: Not Implemented
Handle 0x1900, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: *-* 00:00:00
Handle 0x1B10, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD00
Handle 0x1B11, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD01
Handle 0x1B12, DMI type 126, 12 bytes
Inactive
Handle 0x1B13, DMI type 126, 12 bytes
Inactive
Handle 0x1B14, DMI type 126, 12 bytes
Inactive
Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x8100, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 00 81 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001
Handle 0x8200, DMI type 130, 20 bytes
OEM-specific Type
Header and Data:
82 14 00 82 24 41 4D 54 01 01 00 00 01 A5 0B 02
00 00 00 00
Handle 0x8300, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 00 83 14 00 00 00 00 00 C0 29 05 00 00 00
F8 00 4E 24 00 00 00 00 0D 00 00 00 02 00 03 00
19 04 14 00 01 00 01 02 C8 00 BD 10 00 00 00 00
00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
Handle 0x8800, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 00 88 5A 5A
Handle 0xD000, DMI type 208, 10 bytes
OEM-specific Type
Header and Data:
D0 0A 00 D0 01 03 FE 00 11 02
Handle 0xD100, DMI type 209, 12 bytes
OEM-specific Type
Header and Data:
D1 0C 00 D1 78 03 07 03 04 0F 80 05
Handle 0xD200, DMI type 210, 12 bytes
OEM-specific Type
Header and Data:
D2 0C 00 D2 F8 03 04 03 06 80 04 05
Handle 0xD201, DMI type 126, 12 bytes
Inactive
Handle 0xD400, DMI type 212, 242 bytes
OEM-specific Type
Header and Data:
D4 F2 00 D4 70 00 71 00 00 10 2D 2E 42 00 11 FE
01 43 00 11 FE 00 0F 00 25 FC 00 10 00 25 FC 01
11 00 25 FC 02 12 00 25 FC 03 00 00 25 F3 00 00
00 25 F3 04 00 00 25 F3 08 00 00 25 F3 0C 07 00
23 8F 00 08 00 23 F3 00 09 00 23 F3 04 0A 00 23
F3 08 0B 00 23 8F 10 0C 00 23 8F 20 0E 00 23 8F
30 0D 00 23 8C 40 A6 00 23 8C 41 A7 00 23 8C 42
05 01 22 FD 02 06 01 22 FD 00 8C 00 22 FE 00 8D
00 22 FE 01 9B 00 25 3F 40 9C 00 25 3F 00 09 01
25 3F 80 A1 00 26 F3 00 A2 00 26 F3 08 A3 00 26
F3 04 9F 00 26 FD 02 A0 00 26 FD 00 9D 00 11 FB
04 9E 00 11 FB 00 54 01 23 7F 00 55 01 23 7F 80
5C 00 78 BF 40 5D 00 78 BF 00 04 80 78 F5 0A 01
A0 78 F5 00 93 00 7B 7F 80 94 00 7B 7F 00 8A 00
37 DF 20 8B 00 37 DF 00 03 C0 67 00 05 FF FF 00
00 00
Handle 0xD401, DMI type 212, 172 bytes
OEM-specific Type
Header and Data:
D4 AC 01 D4 70 00 71 00 03 40 59 6D 2D 00 59 FC
02 2E 00 59 FC 00 6E 00 59 FC 01 E0 01 59 FC 03
28 00 59 3F 00 29 00 59 3F 40 2A 00 59 3F 80 2B
00 5A 00 00 2C 00 5B 00 00 55 00 59 F3 00 6D 00
59 F3 04 8E 00 59 F3 08 8F 00 59 F3 00 00 00 55
FB 04 00 00 55 FB 00 23 00 55 7F 00 22 00 55 7F
80 F5 00 58 BF 40 F6 00 58 BF 00 EB 00 55 FE 00
EA 00 55 FE 01 40 01 54 EF 00 41 01 54 EF 10 ED
00 54 F7 00 F0 00 54 F7 08 4A 01 53 DF 00 4B 01
53 DF 20 4C 01 53 7F 00 4D 01 53 7F 80 68 01 56
BF 00 69 01 56 BF 40 FF FF 00 00 00
Handle 0xD402, DMI type 212, 152 bytes
OEM-specific Type
Header and Data:
D4 98 02 D4 70 00 71 00 00 10 2D 2E 2D 01 21 FE
01 2E 01 21 FE 00 97 00 22 FB 00 98 00 22 FB 04
90 00 11 CF 00 91 00 11 CF 20 92 00 11 CF 10 E2
00 27 7F 00 E3 00 27 7F 80 E4 00 27 BF 00 E5 00
27 BF 40 D1 00 22 7F 80 D2 00 22 7F 00 45 01 22
BF 40 44 01 22 BF 00 36 01 21 F1 06 37 01 21 F1
02 38 01 21 F1 00 39 01 21 F1 04 2B 01 11 7F 80
2C 01 11 7F 00 4E 01 65 CF 00 4F 01 65 CF 10 D4
01 65 F3 00 D5 01 65 F3 04 D2 01 65 FC 00 D3 01
65 FC 01 FF FF 00 00 00
Handle 0xD403, DMI type 212, 157 bytes
OEM-specific Type
Header and Data:
D4 9D 03 D4 70 00 71 00 03 40 59 6D 17 01 52 FE
00 18 01 52 FE 01 19 01 52 FB 00 1A 01 52 FB 04
1B 01 52 FD 00 1C 01 52 FD 02 1D 01 52 F7 00 1E
01 52 F7 08 1F 01 52 EF 00 20 01 52 EF 10 21 01
52 BF 00 22 01 52 BF 40 87 00 59 DF 20 88 00 59
DF 00 E8 01 66 FD 00 E9 01 66 FD 02 02 02 53 BF
00 03 02 53 BF 40 04 02 53 EF 00 05 02 53 EF 10
06 02 66 DF 00 07 02 66 DF 20 08 02 66 EF 00 09
02 66 EF 10 17 02 66 F7 00 18 02 66 F7 08 44 02
52 BF 40 45 02 52 BF 00 FF FF 00 00 00
Handle 0xD800, DMI type 126, 9 bytes
Inactive
Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 00 DD 00 01 00 00 00 10 F5 00 00 00 00 00
00 00 00
Handle 0xDD01, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 01 DD 00 01 00 00 00 11 F5 00 00 00 00 00
00 00 00
Handle 0xDD02, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 02 DD 00 01 00 00 00 12 F5 00 00 00 00 00
00 00 00
Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 00 DE C1 0B 00 00 10 05 19 21 01 00 00 01
Handle 0x7F00, DMI type 127, 4 bytes
End Of Table
Hdparm also does not tell me the max data transfer rate (disk speed) of my current drive although this link : www.wdc.com/en/library/sata/2879-001146.pdf says that it is 3.0Gb/s
and here's hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD800JD-75JNC0
Firmware Revision: 06.01C06
Standards:
Supported: 6 5 4
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156250000
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 76293 MBytes
device size with M = 1000*1000: 80000 MBytes (80 GB)
cache/buffer size = 8192 KBytes
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 8
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
Automatic Acoustic Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* SMART error logging
* SMART self-test
* Gen1 signaling speed (1.5Gb/s)
* Host-initiated interface power management
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct
Last edited by Inxsible (2011-03-27 04:40:49)

I just checked my BIOS and my current setting is set at IDE although it also mentions that the default should be AHCI. Currently I have a dual boot of Windows 7 (need it for Tax software) and Arch
So I guess, when I get the new HDD, I will first set it to AHCI and then install the OSes on it. See if NCQ helps any, and if not I will turn it back and re-install (if I have to). I am planning to have Windows only in virtualbox in the new drive.
Anyhoo, while I was in the BIOS I found two things which I had questions about :
1) Under Onboard Devices --> Integrated NIC , my setting is currently set at "On w/PXE" and it says the default should be just "On". Would it be ok to change it back to On since its a single machine and its not booting an OS on any server. I just don't want to have to re-install anything now since I will be doing that in the new HDD.
2) How would I know whether my BIOS would support a 64 bit OS in Virtualbox? I checked some setting under Virtualization, but they weren't very clear.
I will edit this post and let you know exactly what settings were present under the Virtualization sub-section.

Array mapping to AXIS tdata

Similar Messages

Maybe you are looking for