public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
* Welcome + Boot Error
@ 2006-08-08 12:57 Abot Botbot
  2006-08-09 14:26 ` NFS Bootargs Abot Botbot
  0 siblings, 1 reply; 10+ messages in thread
From: Abot Botbot @ 2006-08-08 12:57 UTC (permalink / raw)
  To: linux-omap-open-source

Hello,

This is my first post to this list. I have participated in several embedded 
linux forums before, including but not limmited to uClinux-microblaze, 
uClinux-dev, google groups such as ARM and ARCH.Embedded, etc. Thanks for 
having me and I hope I can be a useful member of the community. Now to the 
dirty business.


I'm working with the OMAP5912 OSK, an EVM board from Spectrum Digital. I've 
gone through all the steps of building the kernel, building my apps, and all 
that. I've set up my new file system with my compiled apps as an NFS share 
which I can successfully mount from the EVM board as well as other systems 
on the network. When I boot my board it should mount this file system and 
boot, but instead I see the following error:

.... boot log ....
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com
RAMDISK: Couldn't find valid RAM disk image starting at 0.
Freeing initrd memory: 8192K
Looking up port of RPC 100003/2 on [[[myip]]]
Looking up port of RPC 100005/1 on [[[myip]]]
VFS: Mounted root (nfs filesystem).
Mounted devfs on /dev
Freeing init memory: 64K
Kernel panic: No init found.  Try passing init= option to kernel.

My bootargs from uBoot are as follows:

bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs 
nfsroot=[[[myip]]]:/home/projects/filesys,nolock mem=30M

I tried putting a init=/bin/sh in this string in a few different places and 
as its own parameter, but that doesnt seem to solve the problem. Does anyone 
have any ideas?

Thanks,
Andy

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: NFS Bootargs
@ 2006-08-09 19:55 Abot Botbot
  0 siblings, 0 replies; 10+ messages in thread
From: Abot Botbot @ 2006-08-09 19:55 UTC (permalink / raw)
  To: linux-omap-open-source

[-- Attachment #1: Type: text/plain, Size: 6716 bytes --]

Daan,

   The raw console output as captured by hyperterminal is attached. I have 
to head out now but I will do more tomorrow on this issue. Seriously, thanks 
so much for your help.

Thanks,
Andy



>From: "Daan Biere" <webwire@zonnet.nl>
>Reply-To: "Daan Biere" <webwire@zonnet.nl>
>To: "Abot Botbot" <dejanigma@hotmail.com>
>Subject: Re: NFS Bootargs
>Date: Wed, 9 Aug 2006 21:08:21 +0200
>
>Hey :)
>i made the script because i'll make alot of filesystems for development 
>purposes, the script is just to use if you have an empty directory and want 
>to build your own distribution, if you run the script in the /nfsroot/lib 
>directory with parameter "/bin/bash" it will copy all needed libs to that 
>directory, but if you already have the nfsroot it shouldn't be necessary.
>Did you already check in the /var/log/daemon.log if the nfs root is being 
>accessed by the nfs client?, if not you should check your kernel build 
>again, i'm not aware of your linux experience but iits better to explain 
>then not.
>
>In the menuconfig of your kernel you have to check the following options:
>
>    File systems  --->      Network File Systems  --->
>  x x                         <*> NFS file system support x x
>  x x                         [*]   Provide NFSv3 client support x x
>  x x                         [*]     Provide client support for the NFSv3 
>ACL protocol extension                             x x
>  x x                         [*]   Provide NFSv4 client support 
>(EXPERIMENTAL)                                               x x
>  x x                         [*]   Allow direct I/O on NFS files 
>(EXPERIMENTAL)                                              x x
>  x x                         <*> NFS server support x x
>  x x                         [*]   Provide NFSv3 server support x x
>  x x                         [*]     Provide server support for the NFSv3 
>ACL protocol extension                             x x
>  x x                         [*]     Provide NFSv4 server support 
>(EXPERIMENTAL)                                             x x
>  x x                         ---   Provide NFS server over TCP support x x
>  x x                         [*] Root file system on NFS x x
>
>
>Can you give me an output of the kernel messages so i can check what errors 
>could cause the problem?
>
>
>----- Original Message ----- From: "Abot Botbot" <dejanigma@hotmail.com>
>To: <linux-omap-open-source@linux.omap.com>
>Sent: Wednesday, August 09, 2006 8:18 PM
>Subject: Re: NFS Bootargs
>
>
>>Daan,
>>
>>
>>   Thanks so much for your quick reply. I checked my lib folder, it was 
>>fully populated with everything I need and the perms are set correctly. 
>>This was taken care of during the "make modules" and "make 
>>INSTALL_MOD_PATH..." stuff. I haven't bashed your script yet just because 
>>I'm not too clear what the regexp is doing, but I assume that its looking 
>>for the correct version numbers and copying the appropraite files. Would I 
>>run this from the /filesys/lib directory? Also, the "lddcopy /bin/bash" 
>>line, should that be run from /filesys/lib to /filesys/bin/sh (not bash?)? 
>>I haven't run accross a document that entailed that any of the libraries 
>>should end up in that place, though I am pretty new to this process. 
>>Thanks again for your help, and don't feel obligated to waste more time on 
>>this issue than you feel necessary. Otehrwise, if you do have any other 
>>suggestions I would be glad to hear them.
>>
>>Thanks,
>>Andy
>>
>>
>>>From: "Daan Biere" <webwire@zonnet.nl>
>>>Reply-To: "Daan Biere" <webwire@zonnet.nl>
>>>To: "Abot Botbot" 
>>><dejanigma@hotmail.com>,<linux-omap-open-source@linux.omap.com>
>>>Subject: Re: NFS Bootargs
>>>Date: Wed, 9 Aug 2006 16:45:35 +0200
>>>
>>>Hi Abot,
>>>I've set up a nfsroot yesterday for testing a mips based system, i''m 
>>>using the following bootargs:
>>>
>>>append ip=dhcp nfsroot="192.168.1.101:/home/usr/projects/filesys" 
>>>init=/bin/sh root=/dev/nfs rw
>>>
>>>just be sure you've got all the required depencies in the /lib dir and 
>>>you'll have the /dev/console, i made a little script to do this.
>>>
>>>
>>>ldd $1 | awk '{ print $3; }' | sed 's/\(\/.*\/\(.*\)\)/\1 \2/g' -\
>>>| xargs -l1 --no-run-if-empty cp
>>>
>>>go to the lib dir and type something like "lddcopy /bin/bash" it would 
>>>copy all the required libs.
>>>
>>>Kind Regards,
>>>Daan Biere
>>>----- Original Message ----- From: "Abot Botbot" <dejanigma@hotmail.com>
>>>To: <linux-omap-open-source@linux.omap.com>
>>>Sent: Wednesday, August 09, 2006 4:26 PM
>>>Subject: NFS Bootargs
>>>
>>>
>>>>Hello all,
>>>>
>>>>
>>>>    I'm trying to boot off an NFS share as laid out in the OSK Users 
>>>>guide so I can begin my software development process. My buidling of the 
>>>>system with the approrpiate makefiles has all gone seamlessly. I am 
>>>>attempting to boot from the NFS share on my linux machine, which I've 
>>>>demonstrated is possible from a neighboring machine. The error is as 
>>>>follows:
>>>>
>>>>Kernel panic: No init found.  Try passing init= option to kernel.
>>>>
>>>>I have tried putting an "init=/bin/sh" argument into the bootargs 
>>>>string, but that hasn't solved the problem. Does anyone else have a 
>>>>bootargs string for an NFS share that they have used succesfully? Here 
>>>>is the string I am currently using for refference:
>>>>
>>>>console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs 
>>>>nfsroot=192.168.1.101:/home/usr/projects/filesys,nolock mem=30M 
>>>>init=/bin/sh
>>>>
>>>>Thanks for your help,
>>>>Andy
>>>>
>>>>_________________________________________________________________
>>>>Don't just search. Find. Check out the new MSN Search! 
>>>>http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>>>>
>>>>_______________________________________________
>>>>Linux-omap-open-source mailing list
>>>>Linux-omap-open-source@linux.omap.com
>>>>http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>>>
>>
>>_________________________________________________________________
>>Express yourself instantly with MSN Messenger! Download today - it's FREE! 
>>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>>
>>_______________________________________________
>>Linux-omap-open-source mailing list
>>Linux-omap-open-source@linux.omap.com
>>http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

[-- Attachment #2: error.txt --]
[-- Type: text/plain, Size: 9396 bytes --]

**^XB1000000000045a
Š^X^X^X^X^X^X^X^X^X^X^H^H^H^H^H^H^H^H^H^H
U-Boot 1.1.1 (Aug  4 2005 - 10:41:25)

U-Boot code: 11080000 -> 11095DD4  BSS: -> 1109A5A4
RAM Configuration:
Bank #0: 10000000 32 MB
Micron StrataFlash MT28F128J3 device initialized
Flash: 32 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot: 10 \b\b\b 9 \b\b\b 8 \b\b\b 7 \b\b\b 6 \b\b\b 5 \b\b\b 4 \b\b\b 3 
\b\b\b 2 \b\b\b 1 \b\b\b 0
## Booting image at 00100000 ...
   Image Name:   Linux-2.4.20_mvl31-omap5912_osk
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    741532 Bytes = 724.2 kB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ...
U-Boot 1.1.1 (Aug  4 2005 - 10:41:25)

U-Boot code: 11080000 -> 11095DD4  BSS: -> 1109A5A4
RAM Configuration:
Bank #0: 10000000 32 MB
Micron StrataFlash MT28F128J3 device initialized
Flash: 32 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot: 10 \b\b\b 9 \b\b\b 8 \b\b\b 7 \b\b\b 6 \b\b\b 5 \b\b\b 4 \b\b\b 3 
\b\b\b 2 \b\b\b 1 \b\b\b 0
## Booting image at 00100000 ...
   Image Name:   Linux-2.4.20_mvl31-omap5912_osk
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    741532 Bytes = 724.2 kB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux................................................... done, 
booting the kernel.

CPU: ARM926EJ-Sid(wb) [41069263] revision 3 (ARMv?(8))

CPU: D undefined 14 cache

CPU: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets

CPU: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets

Machine: OMAP5912 OSK/OMAP1610

On node 0 totalpages: 8192

zone(0): 8192 pages.

zone(1): 0 pages.

zone(2): 0 pages.

Kernel command line: console=ttyS0,115200n8 ip=dhcp 
nfsroot=130.215.17.144:/home/dejanigma/projects/filesys init=/bin/sh 
root=/dev/nfs rw

Calibrating delay loop... 95.84 BogoMIPS

Memory: 32MB = 32MB total

Memory: 22484KB available (1352K code, 282K data, 64K init)

Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)

Inode cache hash table entries: 2048 (order: 2, 16384 bytes)

Mount-cache hash table entries: 512 (order: 0, 4096 bytes)

Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)

Page-cache hash table entries: 8192 (order: 3, 32768 bytes)

POSIX conformance testing by UNIFIX

Linux NET4.0 for Linux 2.4

Based upon Swansea University Computer Society NET3.039

Initializing RT netlink socket

LSP Revision 33

ikconfig 0.5 with /proc/ikconfig

Starting kswapd

Disabling the Out Of Memory Killer

devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)

devfs: boot_options: 0x1

JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis 
Communications AB.

i2c-core.o: i2c core module version 2.6.2 (20011118)

pty: 256 Unix98 ptys configured

Serial driver version 5.05c (2001-07-08) with no serial options enabled

ttyS00 at 0xfffb0000 (irq = 46) is a OMAP UART

rtc: RTC power up reset detected.

rtc: Enabling RTC.

Real Time Clock Driver v1.0

watchdog: TI OMAP Watchdog Timer: timer margin 19 sec

smc9194.c:v0.15 12/15/00 by Erik Stahlman (erik@vt.edu)

eth0: SMC91C94/91C96 (rev 9) at 0xe8000000 IRQ:160 INTF:TP MEM:6144b ADDR: 
00:0e:99:02:0d:46

RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize

loop: loaded (max 8 devices)

OMAP1610 I2C INFO: Driver ver. 1.1

TPS65010 driver successfully loaded

OMAP1610 audio support initialized

cfi_cmdset_0001: Erase suspend on write enabled

Using buffer write method

OMAP flash: CFI device at 0x00000000, 16MiB, 16-bit

cfi_cmdset_0001: Erase suspend on write enabled

Using buffer write method

OMAP flash: CFI device at 0x01000000, 16MiB, 16-bit

Concatenating MTD devices:

(0): "<NULL>"

(1): "<NULL>"

into device "omap-flash"

No RedBoot partition table detected in omap-flash

OMAP flash: using static partition definition

Creating 5 MTD partitions on "omap-flash":

0x00000000-0x00020000 : "BootLoader"

0x00020000-0x00040000 : "Params"

0x00040000-0x00240000 : "Kernel"

0x00240000-0x01000000 : "Flash0 FileSys"

0x01000000-0x02000000 : "Flash1 FileSys"

Linux Kernel Card Services 3.1.22

  options:  none

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 2048 bind 4096)

Sending DHCP requests ., OK

IP-Config: Got DHCP answer from 0.0.0.0, my addr

U-Boot 1.1.1 (Aug  4 2005 - 10:41:25)

U-Boot code: 11080000 -> 11095DD4  BSS: -> 1109A5A4
RAM Configuration:
Bank #0: 10000000 32 MB
Micron StrataFlash MT28F128J3 device initialized
Flash: 32 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot: 10 \b\b\b 9 \b\b\b 8 \b\b\b 7 \b\b\b 6 \b\b\b 5 \b\b\b 4 \b\b\b 3 
\b\b\b 2 \b\b\b 1 \b\b\b 0
## Booting image at 00100000 ...
   Image Name:   Linux-2.4.20_mvl31-omap5912_osk
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    741532 Bytes = 724.2 kB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux................................................... done, 
booting the kernel.

CPU: ARM926EJ-Sid(wb) [41069263] revision 3 (ARMv?(8))

CPU: D undefined 14 cache

CPU: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets

CPU: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets

Machine: OMAP5912 OSK/OMAP1610

On node 0 totalpages: 8192

zone(0): 8192 pages.

zone(1): 0 pages.

zone(2): 0 pages.

Kernel command line: console=ttyS0,115200n8 ip=dhcp 
nfsroot=130.215.17.144:/home/dejanigma/projects/filesys init=/bin/sh 
root=/dev/nfs rw

Calibrating delay loop... 95.84 BogoMIPS

Memory: 32MB = 32MB total

Memory: 22484KB available (1352K code, 282K data, 64K init)

Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)

Inode cache hash table entries: 2048 (order: 2, 16384 bytes)

Mount-cache hash table entries: 512 (order: 0, 4096 bytes)

Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)

Page-cache hash table entries: 8192 (order: 3, 32768 bytes)

POSIX conformance testing by UNIFIX

Linux NET4.0 for Linux 2.4

Based upon Swansea University Computer Society NET3.039

Initializing RT netlink socket

LSP Revision 33

ikconfig 0.5 with /proc/ikconfig

Starting kswapd

Disabling the Out Of Memory Killer

devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)

devfs: boot_options: 0x1

JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis 
Communications AB.

i2c-core.o: i2c core module version 2.6.2 (20011118)

pty: 256 Unix98 ptys configured

Serial driver version 5.05c (2001-07-08) with no serial options enabled

ttyS00 at 0xfffb0000 (irq = 46) is a OMAP UART

rtc: RTC power up reset detected.

rtc: Enabling RTC.

Real Time Clock Driver v1.0

watchdog: TI OMAP Watchdog Timer: timer margin 19 sec

smc9194.c:v0.15 12/15/00 by Erik Stahlman (erik@vt.edu)

eth0: SMC91C94/91C96 (rev 9) at 0xe8000000 IRQ:160 INTF:TP MEM:6144b ADDR: 
00:0e:99:02:0d:46

RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize

loop: loaded (max 8 devices)

OMAP1610 I2C INFO: Driver ver. 1.1

TPS65010 driver successfully loaded

OMAP1610 audio support initialized

cfi_cmdset_0001: Erase suspend on write enabled

Using buffer write method

OMAP flash: CFI device at 0x00000000, 16MiB, 16-bit

cfi_cmdset_0001: Erase suspend on write enabled

Using buffer write method

OMAP flash: CFI device at 0x01000000, 16MiB, 16-bit

Concatenating MTD devices:

(0): "<NULL>"

(1): "<NULL>"

into device "omap-flash"

No RedBoot partition table detected in omap-flash

OMAP flash: using static partition definition

Creating 5 MTD partitions on "omap-flash":

0x00000000-0x00020000 : "BootLoader"

0x00020000-0x00040000 : "Params"

0x00040000-0x00240000 : "Kernel"

0x00240000-0x01000000 : "Flash0 FileSys"

0x01000000-0x02000000 : "Flash1 FileSys"

Linux Kernel Card Services 3.1.22

  options:  none

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 2048 bind 4096)

Sending DHCP requests ., OK

IP-Config: Got DHCP answer from 0.0.0.0, my address is 130.215.18.10

IP-Config: Complete:

      device=eth0, addr=130.215.18.10, mask=255.255.248.0, gw=130.215.16.1,

     host=andyd_evm.ece.wpi.edu, domain=ece.wpi.edu, nis-domain=(none),

     bootserver=0.0.0.0, rootserver=130.215.17.144, rootpath=

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>

All bugs added by David S. Miller <davem@redhat.com>

NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com

RAMDISK: Couldn't find valid RAM disk image starting at 0.

Freeing initrd memory: 8192K

Looking up port of RPC 100003/2 on 130.215.17.144

Looking up port of RPC 100005/1 on 130.215.17.144

VFS: Mounted root (nfs filesystem).

Mounted devfs on /dev

Freeing init memory: 64K

Kernel panic: No init found.  Try passing init= option to kernel.


[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: NFS Bootargs
@ 2006-08-10  5:06 Manoj Kotnala
  0 siblings, 0 replies; 10+ messages in thread
From: Manoj Kotnala @ 2006-08-10  5:06 UTC (permalink / raw)
  To: linux-omap-open-source


Andy,

Are you using BusyBox?
If yes, you need to enable one option in Busybox config (related to NFS support)..

Regards,

Manoj Kotnala




-----Original Message-----
From: linux-omap-open-source-bounces@linux.omap.com [mailto:linux-omap-open-source-bounces@linux.omap.com] On Behalf Of linux-omap-open-source-request@linux.omap.com
Sent: Thursday, August 10, 2006 10:26 AM
To: linux-omap-open-source@linux.omap.com
Subject: Linux-omap-open-source Digest, Vol 28, Issue 14

Send Linux-omap-open-source mailing list submissions to
	linux-omap-open-source@linux.omap.com

To subscribe or unsubscribe via the World Wide Web, visit
	http://linux.omap.com/mailman/listinfo/linux-omap-open-source
or, via email, send a message with subject or body 'help' to
	linux-omap-open-source-request@linux.omap.com

You can reach the person managing the list at
	linux-omap-open-source-owner@linux.omap.com

When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-omap-open-source digest..."


Today's Topics:

   1. Re: NFS Bootargs (Mark Howell)
   2. Re: ARM: OMAP: Fix OMAP1 compilation after MPUIO check
      change. (Mark Howell)
   3. Re: [PATCH 1/3] aic23: Kconfig fixes for alsa and oss
      drivers. (lamikr)
   4. Re: status of OMAP ALSA support (lamikr)
   5. MCSI & MCBSP howto configure as gpio (Arnold)
   6. Re: Pending July patches (andrzej zaborowski)
   7. RE: MCSI & MCBSP howto configure as gpio (Khasim, Syed)
   8. Re: Suspending with keypad bug (RFC) (andrzej zaborowski)


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

Message: 1
Date: Wed, 09 Aug 2006 16:45:47 -0700
From: Mark Howell <mhowell@northlink.com>
Subject: Re: NFS Bootargs
To: Abot Botbot <dejanigma@hotmail.com>
Cc: linux-omap-open-source@linux.omap.com
Message-ID: <44DA73AB.4050104@northlink.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Abot Botbot wrote:
> Hello all,
>
>
>    I'm trying to boot off an NFS share as laid out in the OSK Users
> guide so I can begin my software development process. My buidling of
> the system with the approrpiate makefiles has all gone seamlessly. I
> am attempting to boot from the NFS share on my linux machine, which
> I've demonstrated is possible from a neighboring machine. The error is
> as
> follows:
>
> Kernel panic: No init found.  Try passing init= option to kernel.
>
> I have tried putting an "init=/bin/sh" argument into the bootargs
> string, but that hasn't solved the problem. Does anyone else have a
> bootargs string for an NFS share that they have used succesfully? Here
> is the string I am currently using for refference:
>
> console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs
> nfsroot=192.168.1.101:/home/usr/projects/filesys,nolock mem=30M
> init=/bin/sh
>
> Thanks for your help,
> Andy
>
[snip]

Andy, this is a working NFS boot string for my 1611 H2 with today's git
kernel:

mem=32M console=ttyS0,115200n8 noinitrd root=/dev/nfs rw nfsroot=172.30.2.32:/home/markh/omap/nfsroot ip=dhcp

Cheers,

Mark.



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

Message: 2
Date: Wed, 09 Aug 2006 16:46:39 -0700
From: Mark Howell <mhowell@northlink.com>
Subject: Re: ARM: OMAP: Fix OMAP1 compilation after MPUIO check
	change.
To: linux-omap-open-source@linux.omap.com, Imre Deak
	<imre.deak@solidboot.com>
Message-ID: <44DA73DF.7080308@northlink.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Jonathan McDowell wrote:
> The recent MPUIO range change fix breaks compilation if
> CONFIG_ARCH_OMAP24XX isn't defined; it should be OMAP_MAX_GPIO_LINES
> not MAX_GPIO_LINES I believe. This one liner fixes it.
>

Thanks, this works for me on my 1611 H2 with today's 2.6.18-rc4 from git. Mark.



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

Message: 3
Date: Thu, 10 Aug 2006 03:29:20 +0300
From: lamikr <lamikr@cc.jyu.fi>
Subject: Re: [PATCH 1/3] aic23: Kconfig fixes for alsa and oss
	drivers.
To: Tony Lindgren <tony@atomide.com>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Message-ID: <44DA7DE0.6000200@cc.jyu.fi>
Content-Type: text/plain; charset=ISO-8859-1

Tony Lindgren wrote:
> * lamikr <lamikr@cc.jyu.fi> [060525 13:54]:
>  
>> Kconfig fixes to prevent unselecting I2C and I2C-omap drivers is
>> aic23 sound driver is selected.
>>    
>
> Pushing all 3 patches today.
>
> Tony
>
>  
Tony

I noticed that patches 2 and 3 are not applied. James Selvam tested that they were needed in order to get sounds working with innovator.
Can you you still apply the old patches or should I resend them? (Send originally in 25.5.2006)

In addition to these, audio_process_dma from omap-alsa.c will also need one more fix that I can send separately.
(2 #ifdef CONFIG_MACH_OMAP_H6300 definitions must be changed to #ifdef
CONFIG_ARCH_OMAP15XX)

Mika


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

Message: 4
Date: Thu, 10 Aug 2006 03:42:03 +0300
From: lamikr <lamikr@cc.jyu.fi>
Subject: Re: status of OMAP ALSA support
To: "Zhang, Jian" <jzhang@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Message-ID: <44DA80DB.7010700@cc.jyu.fi>
Content-Type: text/plain; charset=us-ascii

Zhang, Jian wrote:
> Hi,
>
> Does OMAP ALSA driver work? Neither H4 nor H3 has it in default
> configuration.
>  
Yes, the aic23 has been tested with board-osk and tsc2101 has been tested with the board-osk and board-h6300. (h6300 specific code is not yet send to omap-kernel list, but you can check the h6300 port of omap 2.6.16 kernel it by using command:
svn export svn://fuzzyneural.net/h6300/omap-linux/branches/h6300_dev

> I see the following in tsc2101 codec driver:
>
> codec_cfg = pdev->dev.platform_data;
> if (codec_cfg != NULL) {
>  ...
> }
> else
> ret = -ENODEV;
>
> I don't see any code to set up dev.platform_data. As a result,
> codec_cfg is always NULL and OMAP ALSA should not work at all.
>  
It should be pretty easy to add the support also for other omap boards if you just know the correct MCBSP settings. I have not access to h3 or h4 boards so I have not been able to test them. Do you have access to that data?

I have however send once the patches adding a similar kind of support for the Innovator and 770 boards that are using aic23 chipset.
Innovator patches has been tested to work by James Selvam.

According to one message in maemo developer list, somebody build & tested also the 770 patch and was able to hear some kind of noice but not correct sound.
(mcbsp settings were probably incorrect for that board). It seems that n770 uses anyway some other driver for the sounds by default, so I have not investigated this further.

> I might miss something here. Please comment.
>
> Other than that, it seems to have the following limitations by looking
> at the code statically.
> - omap-alsa.c knows the codec connectivity detail (hard-coded to
> MCBSP1). This file should be independent of board specifics.
>  
Maybe that info could also be set-up either during the kernel configuration phase or in board-file.
> - Dead lock as s->dma_lock is double locked in multiple locations.
>  
Hmm, I have not noticed any dead locks. With my h6300 I need however stop sound dma in every round in audio_process_dma() function.
(and according to innovator tests by James Selvam, other omap1510 devices needs to do also the same)

> - Don't support duplex as codec lock is shut off when either input
> stream or output stream is closed.
>  
Do you have any patches for these? If you want I could also try to work with you to fix these issues.
> - Memory strategy is very rudimental: Hard-coded to allocate 128KB
> consistent memory in init time.
>  
Would you like to specify this also in the board file?

Mika


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

Message: 5
Date: Wed, 9 Aug 2006 18:13:30 -0700 (PDT)
From: Arnold <abo_gwapo@yahoo.com>
Subject: MCSI & MCBSP howto configure as gpio
To: linux-omap-open-source@linux.omap.com
Message-ID: <20060810011330.17839.qmail@web55804.mail.re3.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1

Hi All,

Is there anyone who can help me configure MCSI1 or
MCBSP1 to a gpio pin? Is there a spec/howto on how to configure it to a gpio pin? I hope to hear from you guys.

Regards,
OJ

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around http://mail.yahoo.com


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

Message: 6
Date: Thu, 10 Aug 2006 06:41:05 +0200
From: "andrzej zaborowski" <balrog@zabor.org>
Subject: Re: Pending July patches
To: lamikr@cc.jyu.fi
Cc: linux-omap-open-source@linux.omap.com
Message-ID:
	<fb249edb0608092141g71e176e6qe6cabfc245970f36@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 08/08/06, andrzej zaborowski <balrog@zabor.org> wrote:
> On 08/08/06, lamikr <lamikr@cc.jyu.fi> wrote:
> > Tony Lindgren wrote:
> > > * lamikr <lamikr@cc.jyu.fi> [060804 17:40]:
> > >> It would be nice if somebody could test the functionality of usbnet and
> > >> mmc/sd with omap1 devices (omap1510)
> > >> before tagging. I got the lcd working by using the fixes now already
> > >> applied to OMAP kernel but both the MMC/SD
> > >> and usbnet failed to work at least for me & h6300.
> > >> (2.6.16 kernel worked ok.)
> > >>
> > >> I can also try to test again these but for me it will go over the
> > weekend...
> > >
> > > No patches so I tagged it already :)
> > Well, I suppose2.6.17-omap2 tag means that it works with omap2 devices :-)
> >
> > I tried that with my h6340 that but unfortunately I could not find fix
> > for the usbnet and MMC/SD card problems.
> > So it probably means that they are failing also for other OMAP1 devices?
> >
> > I tested usbnet both with the DMA enabled and disabled in omap_udc.c
> > (#define USE_DMA / #undef USE_DMA) and with both of the options
> > the usb link was not created to my desktop.
> > I also tried to mount both the "Kingston Elite Pro 512 MB" SD card and
> > San Disk 256 MB RC-MMC MMC cards without success.
> >
> > With 2.6.16 kernel, both the SD, MMC cards were working as well as the
> > usbnet.
> > Any idea, which would be the best place to add debug in in the MMC/SD
> > card subsystem to get more info?
>
> Try enabling CONFIG_MMC_DEBUG in the config, it should give at least
> some basic info, e.g. what commands are sent to the card and what
> error they give (timeouts, crc..).
>
> Personally I didn't have problems with MMC/SD support on OMAP1 with
> current git, except the 2GB and 4GB cards (but we have a workaround
> for those). Instead I see strange things happen with the LCD -- It
> takes about 1 second to initialise (in 2.6.16 you couldn't notice

Oops, actually it was in the MMC/SD driver. Because the lines
        if (!irqs_disabled())
                return -EAGAIN;
in mmc_omap_suspend were removed, LCD & backlight are now suspended
before MMC and resumed first which results in a weird visual effect
while cards are detected but no slowdown as far as I can tell.

A more serious issue I found in this version on my board (OMAP311) is
that Linux gets really confused if a card is inserted or ejected while
suspended. For example the sequence: suspend the system, eject the
card, resume, suspend again -- results in a lockup in 100% cases while
it worked in 2.6.16. I *think* it's not only me and I *think* it's not
even OMAP specific but can't test it. The lock-up is in
mmc_deselect_cards(), the MMC layer thinks a card is selected (even
though no card is inserted).

> this) and for some reason I had to change the .pixclock field from
> 12500 to 29000. The weird part is that it's not anything in the LCD

I haven't figured out why I had to change the pixclock (debugging is
difficult because 1 in 5 tries it works with the old value so you're
never sure).

> driver because I reverted this driver alone to 2.6.16 and nothing
> changed. I will be investigating this.
>
> >
> > Mika
> >
> > _______________________________________________
> > Linux-omap-open-source mailing list
> > Linux-omap-open-source@linux.omap.com
> > http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> >
>
> Greetings,
> Andrew
> --
> balrog 2oo6
>

It seems a number of things were fixed which weren't broken :P
--
balrog 2oo6


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

Message: 7
Date: Wed, 9 Aug 2006 23:51:47 -0500
From: "Khasim, Syed" <x0khasim@ti.com>
Subject: RE: MCSI & MCBSP howto configure as gpio
To: "Arnold" <abo_gwapo@yahoo.com>,
	<linux-omap-open-source@linux.omap.com>
Message-ID: <77C7F7CB1230A74A9D19C0C111E6EDBEEC6821@DLEE09.ent.ti.com>
Content-Type: text/plain;	charset="us-ascii"

If you have access to TRM of OMAP you are working on, then see the
relevant chapter for pin mux, it should tell you the mode to configure
(inorder to configure a McBSP1 pin as GPIO).

As a hack you can directly write this value to the mux register, but the
correct way would be to add an entry in arch/arm/mach-omap2/mux.c and
use the "omap_cfg_reg" API to configure the same.

Regards,
Khasim

-----Original Message-----
From: linux-omap-open-source-bounces@linux.omap.com
[mailto:linux-omap-open-source-bounces@linux.omap.com] On Behalf Of
Arnold
Sent: Wednesday, August 09, 2006 8:14 PM
To: linux-omap-open-source@linux.omap.com
Subject: MCSI & MCBSP howto configure as gpio

Hi All,

Is there anyone who can help me configure MCSI1 or
MCBSP1 to a gpio pin? Is there a spec/howto on how to
configure it to a gpio pin? I hope to hear from you
guys.

Regards,
OJ

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source


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

Message: 8
Date: Thu, 10 Aug 2006 06:55:26 +0200
From: "andrzej zaborowski" <balrog@zabor.org>
Subject: Re: Suspending with keypad bug (RFC)
To: " Juha Yrj?l? " <juha.yrjola@solidboot.com>
Cc: Linux-OMAP <linux-omap-open-source@linux.omap.com>
Message-ID:
	<fb249edb0608092155r20c17f5dl6397c3d9d191105b@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On 06/08/06, Juha Yrjölä <juha.yrjola@solidboot.com> wrote:
> andrzej zaborowski wrote:
>
> > I came up with a different fix, in the keypad driver but it's a bit
> > more intrusive. With this the device sleeps peacefully until another
> > key-press is detected. What should be the correct behavior?
> > I'm attaching both changes.
>
> This approach is better; the generic PM code should not have to care
> that much about different wakeup sources.
>
> I'm not exactly sure in which state the system is when the suspend
> function is called.  Can there still be timer activity, for example?

I think yes, some suspend functions may rely on timers because they
are not obliged to return immdiately.

> Nevertheless, you're safer doing a spin_lock_irqsave() in the suspend
> function first, and releasing the lock only after setting the suspended
> variable and re-enabling the interrupt.
>
> You should also check whether you're actually running on OMAP1 before
> you write to the register.
>
> In the IRQ handler, you should also do a spin_lock_irqsave() before
> accessing the suspended variable.

Thanks for help! I'm attaching the corrected version, it works nicely.

In the irq handler I release the lock just after accessing the
"suspended" variable because as I understand an irq handler will never
be interrupted by something that calls the suspend function.

>
> Cheers,
> Juha
>


--
balrog 2oo6
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linux-keypad-suspend2.patch
Type: application/octet-stream
Size: 2111 bytes
Desc: not available
Url : http://linux.omap.com/pipermail/linux-omap-open-source/attachments/20060810/57bac840/linux-keypad-suspend2.obj

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

_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source


End of Linux-omap-open-source Digest, Vol 28, Issue 14
******************************************************

============================================================================================================================

Tech Mahindra, formerly Mahindra-British Telecom.

Disclaimer:

This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.

============================================================================================================================

^ permalink raw reply	[flat|nested] 10+ messages in thread
[parent not found: <000501c6bcb1$88fcf3f0$0a02a8c0@DAAN>]
end of thread, other threads:[~2006-08-11 15:06 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-08 12:57 Welcome + Boot Error Abot Botbot
2006-08-09 14:26 ` NFS Bootargs Abot Botbot
2006-08-09 14:45   ` Daan Biere
2006-08-09 18:18     ` Abot Botbot
2006-08-09 23:45   ` Mark Howell
2006-08-10 14:28     ` Abot Botbot
2006-08-10  1:13   ` MCSI & MCBSP howto configure as gpio Arnold
  -- strict thread matches above, loose matches on Subject: below --
2006-08-09 19:55 NFS Bootargs Abot Botbot
2006-08-10  5:06 Manoj Kotnala
     [not found] <000501c6bcb1$88fcf3f0$0a02a8c0@DAAN>
2006-08-11 15:06 ` Abot Botbot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox