How to read ACPI table in Windows

This post is about a general info on how can we read the Advance Configuration and Power Interface (ACPI) which contain various tables (DSDT, APIC, RSDP, RSDT, etc) which tell the OS what they can take control over the system (usually on Power).

For BIOS, we usually care most is the DSDT table - Differentiate System Description Table which is part of ACPI. DSDT provide the interface or supply info on what is supported by the system for the OS to control.

This post is not to explain on every table. It is about how we can read the ACPI table out from our system. We usually call it "how can we dump ACPI table out from out system"
They are different ways to do in Windows and Linux. This post will focus only on Windows for now. I'll write about Linux next time.

In Windows, there are couple of tools we can use to read these tables. I'll share 2:

1) You can download and install R/W Everything. It is the simplest method to read ACPI table. Click on the ACPI and it will show you all the tables information
   http://rweverything.com/

2)
 a) Download and unzip the IASL tools from https://www.acpica.org/
 b) Using command prompt run the following command
     i) iasl -g
    ii) iasl -d ***.dat
  c) The "-g" is to all dump the ACPI table into a *.dat file which contain the machine code.
  d) the -d option is to dissemble the machine code back to asl or dsl code. (ACPI Machine Language)


Hope this post helps.. :) I will share on how to do it in Linux next time.

Working on UEFI development

If you are working on UEFI/EFI development, here's a good site to visit:

http://feishare.com/

According to the site, FEI stand for Firmware Encoding Index

MIT App Inventor

Ever wonder how can we write Google Android Application without even install the Google SDK?
Well, MIT has come out with an web base solution to create Google apps without even the need to install all the tedious work to get started on developing Android application.

The good thing about this web application invetor is that it does not need to have a strong background of programming language. All you need is to link your building logic block together and send to the server for application compilation.

The bad thing about this is that the size generated from the server is much larger than those written in SDK as it include alot of unused library in your app as well.

More to come... <update on this post>

Here's the link:
http://appinventor.mit.edu/

Recovering a deleted file in Clear Case

This post will be update in the future.
When dealing with files in clear case and how to restore it.

http://www-01.ibm.com/support/docview.wss?uid=swg21149206

What is NUMA

Here's an interesting sites which explains about NUMA or Non-Uniform Memory Access.
To understand NUMA we need to understand what is nodes and how does it work in NUMA.

http://www.qdpma.com/systemarchitecture/NUMA.html

http://msdn.microsoft.com/en-us/library/ms178144(v=sql.105).aspx

X86 system programming guide

Here's some info on X86 system programming guide
http://www.intel.com/content/www/us/en/processors/architectures-software-developer-manuals.html

Count Lines of Code

There's a very useful free open source tool available to count the lines of code of your project.
It's called "CLOC" (http://cloc.sourceforge.net/)
It's a very simple tool.
Just download the tool and copy it to the directory/path of your source tree.
Execute the following command in command prompt to get the results:

cloc-1.52 --quiet --report-file=Loc.log *