<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>EmbLogic &#187; iittashish447</title>
	<atom:link href="https://www.emblogic.com/blog/author/iittashish447/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.emblogic.com/blog</link>
	<description>Embedded System and ARM Training</description>
	<lastBuildDate>Tue, 03 Mar 2020 13:00:06 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.1</generator>
	<item>
		<title>Device driver</title>
		<link>https://www.emblogic.com/blog/05/device-driver-12/</link>
		<comments>https://www.emblogic.com/blog/05/device-driver-12/#comments</comments>
		<pubDate>Tue, 13 May 2014 10:06:12 +0000</pubDate>
		<dc:creator><![CDATA[iittashish447]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=10076</guid>
		<description><![CDATA[In computing, a device driver (commonly referred to as simply a driver) is a computer program that operates or controls a particular type of device that is attached to a computer.[1] A driver provides a software interface to hardware devices, &#8230; <a href="https://www.emblogic.com/blog/05/device-driver-12/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>In computing, a <b>device driver</b> (commonly referred to as simply a <b>driver</b>) is a <a title="Computer program" href="http://en.wikipedia.org/wiki/Computer_program">computer program</a> that operates or controls a particular type of device that is attached to a computer.<sup id="cite_ref-dev1_1-0" class="reference"><a href="http://en.wikipedia.org/wiki/Device_driver#cite_note-dev1-1">[1]</a></sup> A driver provides a <a class="mw-redirect" title="Software interface" href="http://en.wikipedia.org/wiki/Software_interface">software interface</a> to hardware devices, enabling operating systems and other computer programs to access hardware functions without needing to know precise details of the hardware being used.</p>
<p>A driver typically communicates with the <a title="Peripheral" href="http://en.wikipedia.org/wiki/Peripheral">device</a> through the <a class="mw-redirect" title="Computer bus" href="http://en.wikipedia.org/wiki/Computer_bus">computer bus</a> or communications subsystem to which the hardware connects. When a calling program invokes a <a title="Subroutine" href="http://en.wikipedia.org/wiki/Subroutine">routine</a> in the driver, the driver issues commands to the device. Once the device sends data back to the driver, the driver may invoke routines in the original calling program. Drivers are hardware-dependent and <a title="Operating system" href="http://en.wikipedia.org/wiki/Operating_system">operating-system</a>-specific. They usually provide the <a title="Interrupt" href="http://en.wikipedia.org/wiki/Interrupt">interrupt</a> handling required for any necessary asynchronous time-dependent hardware interface.</p>
<table class="vertical-navbox nowraplinks" style="float: right;clear: right;width: 377px;margin: 0px 0px 1em 1em;background: none repeat scroll 0% 0% #f9f9f9;border: 1px solid #aaaaaa;padding: 0.2em;border-spacing: 0.4em 0px;text-align: center;line-height: 1.4em;font-size: 88%;height: 641px" cellspacing="5" cellpadding="0">
<tbody>
<tr>
<th style="padding: 0.2em 0.4em 0.2em;;font-size: 145%;line-height: 1.2em"><a title="Operating system" href="http://en.wikipedia.org/wiki/Operating_system">Operating systems</a></th>
</tr>
<tr>
<td style="padding: 0.2em 0 0.4em">
<div class="center">
<div class="floatnone">
<div class="noresize" style="height: 244px;width: 165px">
<map id="ImageMap_1_553394327" name="ImageMap_1_553394327">
<area title="User" alt="User" coords="1,1,165,59" shape="rect" href="http://en.wikipedia.org/wiki/User_%28computing%29" />
<area title="Application" alt="Application" coords="1,60,165,119" shape="rect" href="http://en.wikipedia.org/wiki/Application_software" />
<area title="Operating System" alt="Operating System" coords="1,119,165,178" shape="rect" href="http://en.wikipedia.org/wiki/Operating_system" />
<area title="Hardware" alt="Hardware" coords="1,179,165,237" shape="rect" href="http://en.wikipedia.org/wiki/Personal_computer_hardware" /></map>
<p><img src="http://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Operating_system_placement.svg/165px-Operating_system_placement.svg.png" alt="Operating system placement.svg" usemap="#ImageMap_1_553394327" width="165" height="244" /></p>
<div style="margin-left: 145px;margin-top: -20px;text-align: left"><a title="About this image" href="http://en.wikipedia.org/wiki/File:Operating_system_placement.svg"><img style="border: none" src="http://bits.wikimedia.org/static-1.24wmf3/extensions/ImageMap/desc-20.png" alt="About this image" /></a></div>
</div>
</div>
</div>
</td>
</tr>
<tr>
<th style="padding: 0.1em">Common features</th>
</tr>
<tr>
<td style="padding: 0 0.1em 0.4em;text-align: left">
<ul>
<li><a title="Process management (computing)" href="http://en.wikipedia.org/wiki/Process_management_%28computing%29">Process management</a></li>
<li><a title="Interrupt" href="http://en.wikipedia.org/wiki/Interrupt">Interrupts</a></li>
<li><a title="Memory management" href="http://en.wikipedia.org/wiki/Memory_management">Memory management</a></li>
<li><a title="File system" href="http://en.wikipedia.org/wiki/File_system">File system</a></li>
<li><strong class="selflink">Device drivers</strong></li>
<li><a title="Computer network" href="http://en.wikipedia.org/wiki/Computer_network">Networking (TCP/IP, UDP)</a></li>
<li><a title="Computer security" href="http://en.wikipedia.org/wiki/Computer_security">Security (Process/Memory protection)</a></li>
<li><a title="Input/output" href="http://en.wikipedia.org/wiki/Input/output">I/O</a></li>
</ul>
</td>
</tr>
<tr>
<td style="text-align: right;font-size: 115%"></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/05/device-driver-12/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Character Device Driver</title>
		<link>https://www.emblogic.com/blog/05/character-device-driver-9/</link>
		<comments>https://www.emblogic.com/blog/05/character-device-driver-9/#comments</comments>
		<pubDate>Mon, 12 May 2014 05:56:20 +0000</pubDate>
		<dc:creator><![CDATA[iittashish447]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=9986</guid>
		<description><![CDATA[The Internal Representation of Device Numbers Within the kernel, the dev_t type (defined in &#60;linux/types.h&#62;) is used to hold device numbers—both the major and minor parts. As of Version 2.6.0 of the kernel, dev_t is a 32-bit quantity with 12 &#8230; <a href="https://www.emblogic.com/blog/05/character-device-driver-9/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>The Internal Representation of Device Numbers<br />
Within the kernel, the dev_t type (defined in &lt;linux/types.h&gt;) is used to hold device<br />
numbers—both the major and minor parts. As of Version 2.6.0 of the kernel, dev_t is<br />
a 32-bit quantity with 12 bits set aside for the major number and 20 for the minor<br />
number. Your code should, of course, never make any assumptions about the inter-<br />
nal organization of device numbers; it should, instead, make use of a set of macros<br />
found in &lt;linux/kdev_t.h&gt;. To obtain the major or minor parts of a dev_t, use:<br />
MAJOR(dev_t dev);<br />
MINOR(dev_t dev);<br />
If, instead, you have the major and minor numbers and need to turn them into a dev_t,<br />
use:<br />
MKDEV(int major, int minor);<br />
Note that the 2.6 kernel can accommodate a vast number of devices, while previous<br />
kernel versions were limited to 255 major and 255 minor numbers. One assumes</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/05/character-device-driver-9/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PIPE</title>
		<link>https://www.emblogic.com/blog/03/pipe-2/</link>
		<comments>https://www.emblogic.com/blog/03/pipe-2/#comments</comments>
		<pubDate>Tue, 25 Mar 2014 09:47:48 +0000</pubDate>
		<dc:creator><![CDATA[iittashish447]]></dc:creator>
				<category><![CDATA[Project 03: Client Server Communication using Linux and IPC]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=9400</guid>
		<description><![CDATA[The primitive for creating a pipe is the `pipe&#8217; function.  This creates both the reading and writing ends of the pipe.  It is not very useful for a single process to use a pipe to talk to itself.  In typical &#8230; <a href="https://www.emblogic.com/blog/03/pipe-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>The primitive for creating a pipe is the `pipe&#8217; function.  This creates<br />
both the reading and writing ends of the pipe.  It is not very useful<br />
for a single process to use a pipe to talk to itself.  In typical use,<br />
a process creates a pipe just before it forks one or more child<br />
processes (*note Creating a Process::).  The pipe is then used for<br />
communication either between the parent or child processes, or between<br />
two sibling processes.</p>
<p>The `pipe&#8217; function is declared in the header file `unistd.h&#8217;.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/03/pipe-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>what is BIT</title>
		<link>https://www.emblogic.com/blog/03/what-is-bit/</link>
		<comments>https://www.emblogic.com/blog/03/what-is-bit/#comments</comments>
		<pubDate>Mon, 03 Mar 2014 07:44:07 +0000</pubDate>
		<dc:creator><![CDATA[iittashish447]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=8829</guid>
		<description><![CDATA[Bit is a smallest unit of information.For defineing a bit we use the Voltage,Bit recognization,flow of wave or signal.]]></description>
				<content:encoded><![CDATA[<p>Bit is a smallest unit of information.For defineing a bit we use the Voltage,Bit recognization,flow of wave or signal.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/03/what-is-bit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Master arry</title>
		<link>https://www.emblogic.com/blog/02/master-arry/</link>
		<comments>https://www.emblogic.com/blog/02/master-arry/#comments</comments>
		<pubDate>Thu, 20 Feb 2014 16:54:03 +0000</pubDate>
		<dc:creator><![CDATA[iittashish447]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.emblogic.com/blog/?p=8354</guid>
		<description><![CDATA[I have created master array. But the main problem to create master array by pointer. Let see how it is done.]]></description>
				<content:encoded><![CDATA[<p>I have created master array. But the main problem to create master array by pointer.<br />
Let see how it is done.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.emblogic.com/blog/02/master-arry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
