The following article describes how to build an embedded Linux system running inside an emulator which can be used to develop, test and debug target code even without access to target hardware.

The components

To build our emulator we will need the following components:

* Hardware emulator (we’ll use Qemu)
* Minimal Linux root file system containing a C library and Busybox
* The Linux kernel

Installing Qemu

As first step, we will download and install the Qemu emulator. Qemu is an Open Source machine emulator supporting seven target architectures, including x86, MIPS, Arm and PowerPC, creating by Fabrice Ballard.

Depending on the Linux distribution you use as a workstation, you might be able to use the native package management system of the distribution to get do that.

For Debian, Ubuntu and derivatives:

$ sudo apt-get install qemu

For Fedore and derivatives (as root):

# yum install qemu

For other distributions lacking a Qemu package or those wishing to obtain the very latest package. Note that the “i386″ label refers to the host running the emulator and not the target platform:

$ wget http://bellard.org/qemu/qemu-0.9.1-i386.tar.gz
$ cd /
$ sudo tar zxvf qemu-0.9.1-i386.tar.gz

Or, as root:

# tar zxvf qemu-0.9.1-i386.tar.gz

Alternatively, you can download the sources and build the emulator from scratch. This has the added advantage that you can later adapt the emulator to more accurately reflect your actual hardware:

$ wget http://bellard.org/qemu/qemu-0.9.1.tar.gz
$ tar zxvf qemu-0.9.1.tar.gz
$ cd qemu-0.9.1/
$ ./configure
$ make
$ sudo make install

Or, as root:

# make install

Kernel and file system images

The Qemu emulator we have just installed provides a virtual machine mimicking our target hardware. To actually get Linux running on this virtual machine however, we will need to download an image of the Linux kernel and a suitable root file system image for our target architecture.

Luckily, the Qemu project provides several test images for several architectures supported by Qemu that can be used to get a fast start with Qemu as an embedded Linux system emulator.

Go to the Qemu project download page and choose one of the Qemu test disk images suitable for your embedded platform and download it to your Linux host (in this example we use arm):

$ wget http://bellard.org/qemu/arm-test-0.2.tar.gz

Now extract the image:

$ tar zxvf arm-test-0.2.tar.gz
$ cd arm-test

Booting Linux on the emulator

Start up Qemu with the following command line, adjusting the architecture name, kernel file name and root file system image name according to your specific architecture (again, we use arm in this example):

$ qemu-system-arm -kernel zImage.integrator \
-initrd arm_root.img -tftp / -redir tcp:9999::9999

The above command line starts Qemu in system emulation mode, booting into the kernel image zImage.integrator while loading into the virtual machine RAM the arm_root.img file system and instructing Qemu to make your entire host root file system available for access via TFTP from the emulated machine (more on this ahead).

You should now be seeing a window similar to the following in which the emulated LCD display of the board is shown:
Qemu screenshot

Qemu screenshot

You can log-in with the user “root”. No password is required.

Transferring files to and from the host

The emulator and file system are set up to automatically configure a virtual Ethernet interface in the virtual machine with an internal IP. Through that virtual network interface, the emulator is set up to enable transferring of files to and from the host machine file system using the TFTP protocol.

For example, the following command will copy the file “/home/gby/hello_emu” from the host file system to the current directory inside the emulator:

$ tftp -g -r /home/gby/hello_emu -l hello_emu 10.0.2.2

The following command will copy the file “/root/test.log” from the emulator to the host file system directory “/home/gby/”:

$ tftp -p -l/root/test.log -r /home/gby/test.log 10.0.2.2

In addition, you can use the “wget” comment to transfer files using the FTP and HTTP protocol to the emulator from any compatible server accessible in the network:

$ wget http://codefidence.com/some/file

Qemu supports numerous other way to interact with the host and it’s environment, including bridged virtual network interfaces (as opposed to the default NAT used in the example above) which enables both using NFS to communicate with the host as well as remote debugging from the host, VLAN support, exposing the host file system as a FAT file system, mounting disk, flash or CDROM images from the host file system and even using USB devices connected to the host. For more information on these advanced options, please refer to the Qemu user manual.

Debugging user applications

Using the GNU debugger GDBserver agent, we can debug applications running inside the emulator using the GDB debugger on the host. To do this, first copy (using one of the methods outlined above) the “gdbserver” executable to the emulator. Note that you will need a “gdbserver” executable which was built to run on the target architecture (such as Arm, in the example above) and not on the host!

Also note that since the test images do not contain debugging symbols for the system libraries, you will only be able to debug statically compiled application using them. This limitation can be removed by building your own kernel and file system image (see below for more information on this topic).

$ tftp -g -r /home/gby/src/gdb/gdb/gdbserver/gdberver \
-l gdbserver 10.0.2.2

Next, assign the gdbserver binary execute permissions:

$ chmod u+x gdbserver

Now, run the gdbserver agent, instructing it to use port 9999 (which have redirected to the emulator using the qemu command line) to listen for connections from the debugger:

$ gdbserver 0.0.0.0:9999 /bin/myprog

Or, if you wish to attach to an already running program, use:

$ gdbserver 0.0.0.0:9999 --attach 1234

Finally, run the GDB debugger on your host and instruct it to connect to the host local port 9999 (which the emulator is redirected to the virtual machine):

$ arm-linux-gdb target/bin/myprog
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
...
(gdb) set solib-absulote-prefix /dev/null
(gdb) set solib-search-path target/lib/
(gdb) target remote 127.0.0.1:9999

Debugging the kernel

Using the Qemu emulator to debug kernel code is quite straight forward as Qemu incorporates a minimal GDB agent as part of the emulator itself. To debug the Linux kernel running inside the emulator, add the “-s” parameter to the command line used to start Qemu:

$ qemu-system-arm -kernel zImage.integrator \
-initrd arm_root.img -tftp / -redir tcp:9999::9999 -s

Now when the emulator will start, it will wait for a debugger connection on the default port “1234″ (or a different port specific with the “-p” option) , before proceeding with the boot. Once the emulator has started, you can debug the Linux kernel running inside using GDB on the host:

$ arm-linux-gdb linux/vmlinux
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
...
(gdb) target remote 127.0.0.1:1234

You can use GDB as you normally would. For example, type “cont” to launch the kernel:

(gdb) cont

Building your own kernel and file system images

So far we have seen how to use the Qemu emulator with the test kernel and file system images that are available on the Qemu site. To make full use of the emulator, we can create our own custom kernel and file system images that will better reflect the real target we are trying to develop for.

First, query Qemu regarding which boards it can emulate for you chosen architecture. Replace “arm” in the example above with one of: mips, x86_64, ppc or sparc. For i386, simply use “qemu” as the command:

$ qemu-system-arm -M \?

Choose the board that most closely resembles your real target environment. Note that you can add support to Qemu of your specific true board. This requires some programming though and we shall not cover it in this tutorial.

The creation of kernel and file system for our emulated target is no different then doing the same task for a real hardware and in fact. Many tools are freely available to accomplish this task. In this example we shall use the Buildroot framework. Buildroot is a set of make files and patches that makes it easy generate a cross-compilation tool chain and root file system for your target Linux system using the uClibc C library:

First, we shall download the latest Buildroot release from the project web site and extract it:

$ wget http://buildroot.uclibc.org/downloads/snapshots/buildroot-snapshot.tar.bz2
$ tar jxvf buildroot-snapshot.tar.bz2
$ cd buildroot/

Next, let’s configure Buildroot for our chosen target board:

$ make menuconfig

You will be presented with a menu enabling you to pick your architecture, sub-architecture, specific board to build for, GCC and uClibc versions and related details. For each entry of the configuration tool, you can find associated help that describes the purpose of the entry.

At minimum, the following configuration options needs to be set:

* Target Architecture option – choose your target architecture (e.g. arm.)
* Target Architecture Variant option – chose a specific model of the architecture (e.g. arm926t.)
* Target options menu – if the target board you wish to emulate (that is supported by Qemu) is listed, turn on support for that board (e.g. enable the “ARM Ltd. Device Support” menu and inside it choose the “Integrator arm926″ option).
* Toolchain menu – turn on “Build gdb server for the Target” option and if you would like to test C++ programs on the emulator, also the “C++ cross-compiler support” option.
* Target filesystem options menu – enable the “cpio the root filesystem” option and choose the “gzip” compression method. You may also request the file system image to be copied to a specified directory once it is generated here.
*

Kernel menu – choose the “linux (Advanced configuration)” option and pick one of the offered Linux kernel versions of the list offered. Also, select the “zImage” binary format. Here you can also specify a directory to copy the generated kernel to.

In addition, you will need to supply a proper Linux kernel configuration file. Note that you extract the kernel configuration configuration file used to generate the kernel supplied as part of the test images by issuing the following command when inside the emulator:

$ zcat /proc/config.gz > linux.config

Alternatively, Linux provides specific kernel configuration for optimal use with Qemu for some architectures. Run the following command to inspect the default kernel configuration included in a specific Linux kernel version:

$ make help

When you’ve done configuring Buildroot, exit the configuration utility (making sure to OK saving the changes) and type: “make”. Buildroot will now download all required sources and build your new kernel and file system image for you. You should now be able to run the emulator using the kernel and file system image you have just created. Use the file name and path of the zImage binary as a parameter to Qemu “-kernel” option and the file name and path of the file system image to the Qemu “-initrd” parameter, like so:

$ qemu-system-arm -kernel zImage \
-initrd rootfs.arm.cpio.gz -tftp / -redir tcp:9999::9999 -s

This is really nice article.

read the Source below

Source: http://www.linuxinsider.com/rsstory/66878.html

This is my new SEXY Gadget/Phone.
having this specs.....

General 2G Network GSM 850 / 900 / 1800 / 1900
3G Network UMTS 900 / 2100
UMTS 850 / 1900 - American version
Announced 2008, November
Status Available. Released 2008, December
Size Dimensions 113 x 59 x 13 mm, 87 cc
Weight 126 g
Display Type TFT, 16M colors
Size 320 x 240 pixels, 2.36 inches
- Full QWERTY keyboard
Sound Alert types Vibration; Downloadable polyphonic, MP3 ringtones
Speakerphone Yes
- 3.5 mm audio jack
Memory Phonebook Practically unlimited entries and fields, Photocall
Call records Detailed, max 30 days
Internal 120 MB
Card slot microSD (TransFlash), up to 16GB, hotswap, buy memory
Data GPRS Class 32, 100 kbps
HSCSD Yes
EDGE Class 32, 296 kbps
3G Yes, 384 kbps
WLAN Wi-Fi 802.11 b/g
Bluetooth Yes, v2.0 with A2DP
Infrared port No
USB Yes, v2.0 microUSB
Camera Primary 2 MP, 1600x1200 pixels, LED flash
Features Videocalling
Video Yes, QVGA@15fps
Secondary No
Features OS Symbian OS 9.2, Series 60 v3.1 UI
CPU ARM 11 369 MHz processor
Messaging SMS, MMS, Email, Instant Messaging
Browser WAP 2.0/xHTML, HTML
Radio FM radio; Visual radio
Games Downloadable
Colors Ultramarine Blue, Ruby Red
GPS No
Java Yes, MIDP 2.0
- MP3/AAC/MPEG4 player
- Office applications
- Push to talk
- Voice command/dial
- Organizer
- Printing
Battery Standard battery, Li-Po 1500 mAh (BP-4L)
Stand-by Up to 432 h (2G) / 480 h (3G)
Talk time Up to 11 h (2G) / 4 h 40 min (3G)
Music play Up to 18 h

This is year FOSS.in is schduled from 1 to 5 december which is same as 2005 FOSS.in and this reminded me some falshback .

...because it looks like we figured out what the suspend/resume problem was. And as suspected, the actual resource code had nothing what-so-ever to do with it, and was apparently just a trigger for timing.

Several developers on Novell's Mono team leaped into action and worked late into the night so that Linux users will be able to watch the stream with Moonlight, an open source implementation of Silverlight 1.0. Their efforts, which were undertaken in collaboration with Microsoft, have ensured that the PIC stream will be accessible to Linux users who download the Moonlight browser plugin from the project's web site, as well as to PPC Mac users who rely on Microsoft's Silverlight 1.0 plugin.


SRC:--http://arstechnica.com/news.ars/post/20090120-obama-inauguration-shines-on-linux-too-with-moonlight.html

Good one writeen by "Mel reyes"

As all of us i am also wishing happy new year to first of all me and then my all friends then every one else in this world.
As this is a great new year(i don't know why i am writing this but still ).As past year what i acheived i think it is only 30 % of my efficiency and a Hell lot of time i wasted on crappy thing which i used to do in college.

Hopping this year we can or rather I can do my level best and put atleast 75% of my full effort.

But lot of things we have to face this year
Global warming
Global financial meltdown
Global variables(Joking)

see u all
cheers

Enjoy your Work

THis night i am having 104 degree body temparature and acute headache.which totally broken me.
Hopping to get well soon.

Unveiled on Monday by the USB Implementers Forum, the USB 3.0 spec can theoretically support data-transfer speeds of up to 4.8Gbps — 10 times the speed provided by USB 2.0.

The new standard, also known as SuperSpeed USB, is also expected to be more power-efficient than its predecessor.

"SuperSpeed USB is the next advancement in ubiquitous technology," Jeff Ravencraft, the president of the USB Implementers Forum (USB-IF), the industry group that promotes USB technology, said in a statement on Monday. "Today's consumers are using rich media and large digital files that need to be easily and quickly transferred from PCs to devices and vice versa. SuperSpeed USB meets the needs of everyone, from the tech-savvy executive to the average home user."

The USB-IF hopes USB 3.0 will be built into computers from late 2009, with consumer products using the specification starting to appear the following year — or roughly a decade after USB 2.0 made its appearance. According to the industry group, the first such products will include external hard drives, flash drives, digital cameras and personal media players.

The specification was designed to be backwards-compatible with earlier iterations of USB.

SRC:-http://news.zdnet.co.uk/hardware/0,1000000091,39554846,00.htm

This 1:38 am in morning i am thinking what to do and what not do in life.what i did till now (i guess nothing) and what more to do (a hell lot of thing).

just now i came to know about price of Apple Iphone it is 31000(8GB) and 36100(16GB).

really it is too high,although Steve jobs announced that it won't cost more than 200USD world wide and vodafone is taking this much making Hole in our pocket.
rellay Apple pepole should do something for this huge price which is making hole(more than a*s Hole)in our pocket.

Yesterday i promoted as a Software Engineer "a good news after long time".

System Name	Roadrunner
System Family	IBM Cluster
System Model	BladeCenter QS22 Cluster
Computer	BladeCenter QS22/LS21 Cluster, PowerXCell 8i 3.2 Ghz / Opteron DC 1.8 GHz , Voltaire Infiniband
Vendor	IBM
Application area	Not Specified
Installation Year	2008
Operating System	Linux
Interconnect	Infiniband
Processor	PowerXCell 8i 3200 MHz (12.8 GFlops)

Steve Jobs

Let’s start with the man who co-founded Apple in 1976, left the company in 1985, then came back and saved the day in 1997.

1991:

What a computer is to me is the most remarkable tool that we have ever come up with. It’s the equivalent of a bicycle for our minds.

1994, while he was obviously not working at Apple:

If I were running Apple, I would milk the Macintosh for all it’s worth — and get busy on the next great thing. The PC wars are over. Done. Microsoft won a long time ago.

1996, on Bill Gates:

I wish him the best, I really do. I just think he and Microsoft are a bit narrow. He’d be a broader guy if he had dropped acid once or gone off to an ashram when he was younger.

1997, on Apple products:

The products suck! There’s no sex in them anymore!

2003, a modest comment on the iPod and iTunes:

It will go down in history as a turning point for the music industry. This is landmark stuff. I can’t overestimate it!

2006, on Microsoft:

Our friends up north spend over five billion dollars on research and development and all they seem to do is copy Google and Apple.

2007, on his $1 annual salary:

I make fifty cents for showing up … and the other 50 cents is based on my performance.

Bill Gates

Now on to the man who co-founded Microsoft in 1975 and later became the richest man in the world.

1980:

There’s nobody getting rich writing software that I know of.

1983:

We will never make a 32-bit operating system.

1984:

The next generation of interesting software will be done on the Macintosh, not the IBM PC.

1987:

I believe OS/2 is destined to be the most important operating system, and possibly program, of all time.

1991:

If people had understood how patents would be granted when most of today’s ideas were invented, and had taken out patents, the industry would be at a complete standstill today.

1993:

The Internet? We are not interested in it.

1995:

There are no significant bugs in our released software that any significant number of users want fixed.

1996, on the oft-quoted “640K ought to be enough for anybody.”

I’ve said some stupid things and some wrong things, but not that. No one involved in computers would ever say that a certain amount of memory is enough for all time… I keep bumping into that silly quotation attributed to me that says 640K of memory is enough.

1998:

Microsoft looks at new ideas, they don’t evaluate whether the idea will move the industry forward, they ask, ‘how will it help us sell more copies of Windows?’

1998, memo to the Office product group:

One thing we have got to change in our strategy - allowing Office documents to be rendered very well by other people’s browsers is one of the most destructive things we could do to the company. We have to stop putting any effort into this and make sure that Office documents very well depends on PROPRIETARY IE capabilities.

2001:

Microsoft has had clear competitors in the past. It’s a good thing we have museums to document that.

2004:

Spam will be a thing of the past in two years’ time.

Linus Torvalds

Finally, the man who in 1991 started to work on what would become Linux.

1991:

I’m doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones.

1996:

Some people have told me they don’t think a fat penguin really embodies the grace of Linux, which just tells me they have never seen an angry penguin charging at them in excess of 100mph. They’d be a lot more careful about what they say if they had.

1998:

My name is Linus Torvalds and I am your god.

2001:

Do you pine for the days when men were men and wrote their own device drivers?

2003:

Really, I’m not out to destroy Microsoft. That will just be a completely unintentional side effect.

2006:

Talk is cheap. Show me the code.

2006:

Which mindset is right? Mine, of course. People who disagree with me are by definition crazy. (Until I change my mind, when they can suddenly become upstanding citizens. I’m flexible, and not black-and-white.)

2007:

I have an ego the size of a small planet.

2008:

Security people are often the black-and-white kind of people that I can’t stand. I think the OpenBSD crowd is a bunch of masturbating monkeys, in that they make such a big deal about concentrating on security to the point where they pretty much admit that nothing else matters to them





Source:http://royal.pingdom.com/?p=325

Torvalds: not one to mince his words...

1. “Software is like sex: it's better when it's free.”

2. “Microsoft isn't evil, they just make really crappy operating systems.”

3. “My name is Linus, and I am your God.”

4. “See, you not only have to be a good coder to create a system like Linux, you have to be a sneaky bastard too.”

5. “The Linux philosophy is 'Laugh in the face of danger'. Oops. Wrong One. 'Do it yourself'. Yes, that's it.”

6. “Some people have told me they don't think a fat penguin really embodies the grace of Linux, which just tells me they have never seen a angry penguin charging at them in excess of 100 mph.”

7. “Intelligence is the ability to avoid doing work, yet getting the work done.”

8. “When you say, ‘I wrote a program that crashed Windows,’ people just stare at you blankly and say, ‘Hey, I got those with the system, for free.’”

9. “I don't doubt at all that virtualization is useful in some areas. What I doubt rather strongly is that it will ever have the kind of impact that the people involved in virtualization want it to have.”

10. “Now, most of you are probably going to be totally bored out of your minds on Christmas day, and here's the perfect distraction. Test 2.6.15-rc7. All the stores will be closed, and there's really nothing better to do in between meals.”

This i am writing as i have not found any good tutorial on this topic.


to detect the mobile phone first do some workouts like
1. command

sdptool browse

Inquiring ...
Browsing 00:17:B0:B4:52:C8 ...
Service Name: Dial-up networking
Service RecHandle: 0x10010
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1------------------------->note this channel number
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100

2. second command

hcitool scan

Scanning ...
00:17:B0:B4:52:C8 ABHAY





Then write the following scripts

sudo gedit /etc/bluetooth/hcid.conf
---------------------------------------------------------------------------------
#
# HCI daemon configuration file.
#

# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;

# Default PIN code for incoming connections
passkey "1234"; -------------------------------------->>>default passcode in linux that you have to enter in mobile phone
#pin_helper /etc/bluetooth/pin;
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";

# Local device class
class 0x000100;

# Default packet type
#pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}

------------------------------------------------------------------------------------------

sudo gedit /etc/bluetooth/pin

---------------------------------------
#!/bin/sh
echo "PIN:1234"
NOTE:you have to enter the same pin in the mobile for paring
----------------------------------------
sudo gedit /etc/ppp/chat-gprs
---------------------------------------

"ATZ OK
AT+CGDCONT=1,"IP","www"------->this line depends upon carrier for airtel change www to airtelgprs.com
OK "ATD*99***1#"
CONNECT"
---------------------------------------

sudo gedit /etc/ppp/peers/ngage
------------------------------------------------------------------------

connect '/usr/sbin/chat -v -f /etc/chatscripts/ngage'
ipparam ngage
/dev/rfcomm0
115200
crtscts
noccp
noipdefault
usepeerdns
ipcp-accept-remote
ipcp-accept-local
defaultroute
debug
noauth

-------------------------------------------------------------------------


sudo gedit /etc/bluetooth/rfcomm.conf

------------------------------------------------------------------------
rfcomm0 {
bind yes;
device 00:0E:6D:CE:AE:B2; ------>this is ur mobile bluetooth address
channel 1;---------------->This is your channel number
comment "ABHAY";
}
------------------------------------------------------------------------


then run this command

sudo chmod u+x /etc/bluetooth/pin




and finally to connect

run pon ngage or call


to disconnect

run poff ngage

then enjoy surfing

speed is preety good
Download speed around 10 to 15 kbps for EDGE enabled handset.
for non EDGE enabled handset around 6 kbps.

to see the details see /ver/log/messeges

This is my 24th birthday party celebrated with my company friends.

well i turned 24 i saw back and realised that a lot of things are still to be done and almost 2/3rd of life my spent(5 years in shimoga"Wasted")..

lot of things to do..................let's see....