<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Embedded Linux practical labs with the Beagle Board - Free Electrons blog</title>
	<atom:link href="http://free-electrons.com/blog/beagle-labs/feed/" rel="self" type="application/rss+xml" />
	<link>http://free-electrons.com/blog/beagle-labs/</link>
	<description>Embedded Linux Experts</description>
	<lastBuildDate>Mon, 06 Feb 2012 23:08:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Embedded Linux practical labs with the Beagle Board - Free Electrons blog</title>
		<link>http://free-electrons.com/blog/beagle-labs/comment-page-1/#comment-20876</link>
		<dc:creator>Pragnya</dc:creator>
		<pubDate>Wed, 14 Sep 2011 05:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://free-electrons.com/?p=2129#comment-20876</guid>
		<description>Hello sir,

I installed the latest angstrom demo image on beagleboard rev C4 using
SD card. Logged in as root. Pico projector is connected to HDMI port
and shows the login screen. I have a serial port connected with tera
term pro and a mouse and keyboard connected to beagleboard. I can play
the included BigBunny movie on pico projector.
Now my project aim is to use this beagle board as an interface between my system and DLP Pico Projector to configure the projector using i2c commands.
so when i type the following command to check for i2c buses on beagle board it isa displaying the below lines..

root@beagleboard:/dev# ls i2c*
-sh: i2c bus not found

What does it mean? Is that mean the drivers are not there ?
Please help me in finding out what is the problem and what i need to do.
Thank you in advance.</description>
		<content:encoded><![CDATA[<p>Hello sir,</p>
<p>I installed the latest angstrom demo image on beagleboard rev C4 using<br />
SD card. Logged in as root. Pico projector is connected to HDMI port<br />
and shows the login screen. I have a serial port connected with tera<br />
term pro and a mouse and keyboard connected to beagleboard. I can play<br />
the included BigBunny movie on pico projector.<br />
Now my project aim is to use this beagle board as an interface between my system and DLP Pico Projector to configure the projector using i2c commands.<br />
so when i type the following command to check for i2c buses on beagle board it isa displaying the below lines..</p>
<p>root@beagleboard:/dev# ls i2c*<br />
-sh: i2c bus not found</p>
<p>What does it mean? Is that mean the drivers are not there ?<br />
Please help me in finding out what is the problem and what i need to do.<br />
Thank you in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Embedded Linux practical labs with the Beagle Board - Free Electrons blog</title>
		<link>http://free-electrons.com/blog/beagle-labs/comment-page-1/#comment-18278</link>
		<dc:creator>Thomas Petazzoni</dc:creator>
		<pubDate>Mon, 04 Jul 2011 13:57:35 +0000</pubDate>
		<guid isPermaLink="false">http://free-electrons.com/?p=2129#comment-18278</guid>
		<description>Passing root=/dev/nfs is not sufficient, you also need to pass the ip= and nfsroot= options. Moreover, your NFS server must be set up appropriately on your development workstation.</description>
		<content:encoded><![CDATA[<p>Passing root=/dev/nfs is not sufficient, you also need to pass the ip= and nfsroot= options. Moreover, your NFS server must be set up appropriately on your development workstation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Embedded Linux practical labs with the Beagle Board - Free Electrons blog</title>
		<link>http://free-electrons.com/blog/beagle-labs/comment-page-1/#comment-18275</link>
		<dc:creator>abhishek kunwar</dc:creator>
		<pubDate>Mon, 04 Jul 2011 10:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://free-electrons.com/?p=2129#comment-18275</guid>
		<description>Hi&#039;
While booting 2.6.35.8 kernel on beagleboard-xm (A3) I got this kernel panic :
Detailed error:
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device &quot;nfs&quot; or unknown-block(2,0)
Please append a correct &quot;root=&quot; boot option; here are the available partitions:
b300         3870720 mmcblk0 driver: mmcblk
  b301         3863601 mmcblk0p1
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)


I am passing root=/dev/nfs but I don&#039;t know how to solve this issue.</description>
		<content:encoded><![CDATA[<p>Hi&#8217;<br />
While booting 2.6.35.8 kernel on beagleboard-xm (A3) I got this kernel panic :<br />
Detailed error:<br />
Root-NFS: No NFS server available, giving up.<br />
VFS: Unable to mount root fs via NFS, trying floppy.<br />
VFS: Cannot open root device &#8220;nfs&#8221; or unknown-block(2,0)<br />
Please append a correct &#8220;root=&#8221; boot option; here are the available partitions:<br />
b300         3870720 mmcblk0 driver: mmcblk<br />
  b301         3863601 mmcblk0p1<br />
Kernel panic &#8211; not syncing: VFS: Unable to mount root fs on unknown-block(2,0)</p>
<p>I am passing root=/dev/nfs but I don&#8217;t know how to solve this issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Embedded Linux practical labs with the Beagle Board - Free Electrons blog</title>
		<link>http://free-electrons.com/blog/beagle-labs/comment-page-1/#comment-6053</link>
		<dc:creator>vamsi</dc:creator>
		<pubDate>Thu, 28 Oct 2010 17:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://free-electrons.com/?p=2129#comment-6053</guid>
		<description>hi,
i got the beagleboard-xM recently and following your manual to boot up the board. 
 i am tryin to make the boot image on a new MMC card.
i copied the MLO file, uboot.bin(from mkimage) and uImage to the FAT partition. however the board doesnt read from MMC when i turn it on.are there any other files that have to be copied onto the board.i would greatly appreciate your response.

Thanks,
Vamsi</description>
		<content:encoded><![CDATA[<p>hi,<br />
i got the beagleboard-xM recently and following your manual to boot up the board.<br />
 i am tryin to make the boot image on a new MMC card.<br />
i copied the MLO file, uboot.bin(from mkimage) and uImage to the FAT partition. however the board doesnt read from MMC when i turn it on.are there any other files that have to be copied onto the board.i would greatly appreciate your response.</p>
<p>Thanks,<br />
Vamsi</p>
]]></content:encoded>
	</item>
	<item>
		<title>Embedded Linux practical labs with the Beagle Board - Free Electrons blog</title>
		<link>http://free-electrons.com/blog/beagle-labs/comment-page-1/#comment-1435</link>
		<dc:creator>Maciej Wasiel</dc:creator>
		<pubDate>Mon, 09 Aug 2010 18:23:57 +0000</pubDate>
		<guid isPermaLink="false">http://free-electrons.com/?p=2129#comment-1435</guid>
		<description>Found the solution to my post above. ttyS0 has to be changed to ttyS2 in fwlabs/sysdev/xkernel/data/rootfs/etc/inittab file when using initramfs.</description>
		<content:encoded><![CDATA[<p>Found the solution to my post above. ttyS0 has to be changed to ttyS2 in fwlabs/sysdev/xkernel/data/rootfs/etc/inittab file when using initramfs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Embedded Linux practical labs with the Beagle Board - Free Electrons blog</title>
		<link>http://free-electrons.com/blog/beagle-labs/comment-page-1/#comment-1434</link>
		<dc:creator>Maciej Wasiel</dc:creator>
		<pubDate>Mon, 09 Aug 2010 16:24:12 +0000</pubDate>
		<guid isPermaLink="false">http://free-electrons.com/?p=2129#comment-1434</guid>
		<description>Hi,
I&#039;m following your lab instructions and, like some other people on the web who have followed this tutorial, I&#039;ve run into a problem when booting a cross-compiled kernel on my beagle board where the boot process stops after busybox starts up. The following is the serial output:

Texas Instruments X-Loader 1.4.4ss (Aug  8 2010 - 14:57:52)
Beagle Rev C4
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2010.06-00267-gb1f95b4 (Aug 08 2010 - 15:08:09)

OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Board revision Ax/Bx
Die ID #7c4e000400000000040373050f01300b
Hit any key to stop autoboot:  0 
mmc1 is available
reading boot.scr

** Unable to read &quot;boot.scr&quot; from mmc 0:1 **
reading uImage

2291592 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-2.6.35-rc6-dirty
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2291528 Bytes = 2.2 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.35-rc6-dirty (mwasiel@mwasiel-desktop) (gcc version 4.3.2 (crosstool-NG-1.4.2) ) #1 Mon Aug 9 01:21:59 EDT 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 255252k/255252k available, 6892k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)
    lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc00d9000   ( 836 kB)
      .text : 0xc00d9000 - 0xc043d000   (3472 kB)
      .data : 0xc043e000 - 0xc046f8c0   ( 199 kB)
Hierarchical RCU implementation.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
omap_hwmod: l3_hwmod: cannot be enabled (3)
omap_hwmod: l4_core_hwmod: cannot be enabled (3)
omap_hwmod: l4_per_hwmod: cannot be enabled (3)
omap_hwmod: l4_wkup_hwmod: cannot be enabled (3)
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER12 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 489.46 BogoMIPS (lpj=1912832)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
Unable to get DVI reset GPIO
OMAP DMA hardware revision 4.0
bio: create slab  at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850  3150 mV at 3000 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VDVI: 1800 mV normal standby
regulator: VSIM: 1800  3000 mV at 1800 mV normal standby
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) Â© 2001-2006 Red Hat, Inc.
msgmni has been set to 498
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbmon: debugfs is not available
ehci_hcd: USB 2.0 &#039;Enhanced&#039; Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
i2c /dev entries driver
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing init memory: 836K
init started:  BusyBox v1.4.1 (2007-04-20 15:26:03 CEST) multi-call binary
Starting pid 346, console /dev/ttyS2: &#039;/etc/init.d/rcS&#039;
mmc0: new high speed SD card at address 0007
mmcblk0: mmc0:0007 SD02G 1.90 GiB 
 mmcblk0: p1</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I&#8217;m following your lab instructions and, like some other people on the web who have followed this tutorial, I&#8217;ve run into a problem when booting a cross-compiled kernel on my beagle board where the boot process stops after busybox starts up. The following is the serial output:</p>
<p>Texas Instruments X-Loader 1.4.4ss (Aug  8 2010 &#8211; 14:57:52)<br />
Beagle Rev C4<br />
Reading boot sector<br />
Loading u-boot.bin from mmc</p>
<p>U-Boot 2010.06-00267-gb1f95b4 (Aug 08 2010 &#8211; 15:08:09)</p>
<p>OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz<br />
OMAP3 Beagle board + LPDDR/NAND<br />
I2C:   ready<br />
DRAM:  256 MiB<br />
NAND:  256 MiB<br />
In:    serial<br />
Out:   serial<br />
Err:   serial<br />
Board revision Ax/Bx<br />
Die ID #7c4e000400000000040373050f01300b<br />
Hit any key to stop autoboot:  0<br />
mmc1 is available<br />
reading boot.scr</p>
<p>** Unable to read &#8220;boot.scr&#8221; from mmc 0:1 **<br />
reading uImage</p>
<p>2291592 bytes read<br />
Booting from mmc &#8230;<br />
## Booting kernel from Legacy Image at 82000000 &#8230;<br />
   Image Name:   Linux-2.6.35-rc6-dirty<br />
   Image Type:   ARM Linux Kernel Image (uncompressed)<br />
   Data Size:    2291528 Bytes = 2.2 MiB<br />
   Load Address: 80008000<br />
   Entry Point:  80008000<br />
   Verifying Checksum &#8230; OK<br />
   Loading Kernel Image &#8230; OK<br />
OK</p>
<p>Starting kernel &#8230;</p>
<p>Uncompressing Linux&#8230; done, booting the kernel.<br />
Linux version 2.6.35-rc6-dirty (mwasiel@mwasiel-desktop) (gcc version 4.3.2 (crosstool-NG-1.4.2) ) #1 Mon Aug 9 01:21:59 EDT 2010<br />
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f<br />
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache<br />
Machine: OMAP3 Beagle Board<br />
Memory policy: ECC disabled, Data cache writeback<br />
OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp )<br />
SRAM: Mapped pa 0&#215;40200000 to va 0xfe400000 size: 0&#215;100000<br />
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024<br />
Kernel command line: console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait<br />
PID hash table entries: 1024 (order: 0, 4096 bytes)<br />
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)<br />
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)<br />
Memory: 128MB 128MB = 256MB total<br />
Memory: 255252k/255252k available, 6892k reserved, 0K highmem<br />
Virtual kernel memory layout:<br />
    vector  : 0xffff0000 &#8211; 0xffff1000   (   4 kB)<br />
    fixmap  : 0xfff00000 &#8211; 0xfffe0000   ( 896 kB)<br />
    DMA     : 0xffc00000 &#8211; 0xffe00000   (   2 MB)<br />
    vmalloc : 0xd0800000 &#8211; 0xf8000000   ( 632 MB)<br />
    lowmem  : 0xc0000000 &#8211; 0xd0000000   ( 256 MB)<br />
    modules : 0xbf000000 &#8211; 0xc0000000   (  16 MB)<br />
      .init : 0xc0008000 &#8211; 0xc00d9000   ( 836 kB)<br />
      .text : 0xc00d9000 &#8211; 0xc043d000   (3472 kB)<br />
      .data : 0xc043e000 &#8211; 0xc046f8c0   ( 199 kB)<br />
Hierarchical RCU implementation.<br />
        Verbose stalled-CPUs detection is disabled.<br />
NR_IRQS:402<br />
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz<br />
omap_hwmod: l3_hwmod: cannot be enabled (3)<br />
omap_hwmod: l4_core_hwmod: cannot be enabled (3)<br />
omap_hwmod: l4_per_hwmod: cannot be enabled (3)<br />
omap_hwmod: l4_wkup_hwmod: cannot be enabled (3)<br />
Reprogramming SDRC clock to 332000000 Hz<br />
GPMC revision 5.0<br />
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts<br />
Total of 96 interrupts on 1 active controller<br />
OMAP GPIO hardware version 2.5<br />
OMAP clockevent source: GPTIMER12 at 32768 Hz<br />
Console: colour dummy device 80&#215;30<br />
Calibrating delay loop&#8230; 489.46 BogoMIPS (lpj=1912832)<br />
pid_max: default: 32768 minimum: 301<br />
Mount-cache hash table entries: 512<br />
CPU: Testing write buffer coherency: ok<br />
regulator: core version 0.5<br />
NET: Registered protocol family 16<br />
Found NAND on CS0<br />
Registering NAND on CS0<br />
Unable to get DVI reset GPIO<br />
OMAP DMA hardware revision 4.0<br />
bio: create slab  at 0<br />
SCSI subsystem initialized<br />
usbcore: registered new interface driver usbfs<br />
usbcore: registered new interface driver hub<br />
usbcore: registered new device driver usb<br />
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz<br />
twl4030: PIH (irq 7) chaining IRQs 368..375<br />
twl4030: power (irq 373) chaining IRQs 376..383<br />
twl4030: gpio (irq 368) chaining IRQs 384..401<br />
regulator: VUSB1V5: 1500 mV normal standby<br />
regulator: VUSB1V8: 1800 mV normal standby<br />
regulator: VUSB3V1: 3100 mV normal standby<br />
twl4030_usb twl4030_usb: Initialized TWL4030 USB module<br />
regulator: VMMC1: 1850  3150 mV at 3000 mV normal standby<br />
regulator: VDAC: 1800 mV normal standby<br />
regulator: VDVI: 1800 mV normal standby<br />
regulator: VSIM: 1800  3000 mV at 1800 mV normal standby<br />
i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz<br />
Switching to clocksource 32k_counter<br />
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0<br />
musb_hdrc musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92<br />
NET: Registered protocol family 2<br />
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)<br />
TCP established hash table entries: 8192 (order: 4, 65536 bytes)<br />
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)<br />
TCP: Hash tables configured (established 8192 bind 8192)<br />
TCP reno registered<br />
UDP hash table entries: 256 (order: 0, 4096 bytes)<br />
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)<br />
NET: Registered protocol family 1<br />
RPC: Registered udp transport module.<br />
RPC: Registered tcp transport module.<br />
RPC: Registered tcp NFSv4.1 backchannel transport module.<br />
NetWinder Floating Point Emulator V0.97 (double precision)<br />
VFS: Disk quotas dquot_6.5.2<br />
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)<br />
JFFS2 version 2.2. (NAND) Â© 2001-2006 Red Hat, Inc.<br />
msgmni has been set to 498<br />
alg: No test for stdrng (krng)<br />
io scheduler noop registered<br />
io scheduler deadline registered<br />
io scheduler cfq registered (default)<br />
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled<br />
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654<br />
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654<br />
serial8250.2: ttyS2 at MMIO 0&#215;49020000 (irq = 74) is a ST16654<br />
console [ttyS2] enabled<br />
brd: module loaded<br />
loop: module loaded<br />
usbmon: debugfs is not available<br />
ehci_hcd: USB 2.0 &#8216;Enhanced&#8217; Host Controller (EHCI) Driver<br />
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller<br />
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1<br />
ehci-omap ehci-omap.0: irq 77, io mem 0&#215;48064800<br />
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00<br />
hub 1-0:1.0: USB hub found<br />
hub 1-0:1.0: 3 ports detected<br />
i2c /dev entries driver<br />
TCP cubic registered<br />
NET: Registered protocol family 17<br />
NET: Registered protocol family 15<br />
Power Management for TI OMAP3.<br />
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1<br />
regulator_init_complete: incomplete constraints, leaving VDVI on<br />
regulator_init_complete: incomplete constraints, leaving VDAC on<br />
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)<br />
Freeing init memory: 836K<br />
init started:  BusyBox v1.4.1 (2007-04-20 15:26:03 CEST) multi-call binary<br />
Starting pid 346, console /dev/ttyS2: &#8216;/etc/init.d/rcS&#8217;<br />
mmc0: new high speed SD card at address 0007<br />
mmcblk0: mmc0:0007 SD02G 1.90 GiB<br />
 mmcblk0: p1</p>
]]></content:encoded>
	</item>
</channel>
</rss>

