Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-14 Thread Bryan Wu
On Tue, Sep 14, 2010 at 12:01 PM, Ghorai, Sukumar s-gho...@ti.com wrote:


 -Original Message-
 From: Ricardo Salveti [mailto:rsalv...@rsalveti.net]
 Sent: Tuesday, September 14, 2010 12:22 AM
 To: Ghorai, Sukumar
 Cc: Shilimkar, Santosh; Kevin Hilman; linux-omap@vger.kernel.org;
 t...@atomide.com; Bryan Wu
 Subject: Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0

 On Mon, Sep 13, 2010 at 12:06 PM, Ghorai, Sukumar s-gho...@ti.com wrote:
[Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3,
  4430
   ES2.0 SDP, Blaze and Panda and all booting fine.
   
And omap_4430sdp_defconfig also ok omap4.
  
   Which Panda version are you using during your tests? I tried
   omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and
 I'm
   unable to detect the MMC.
  
   Do I need any other patch to make the MMC work with Panda?
   [Ghorai] I have tested based on following tree/branch and using ES2.0
  PANDA only. Can you share bootlog enabling mmc/sd debug message?
   http://dev.omapzoom.org/?p=santosh/kernel-omap4-
  base.git;a=shortlog;h=refs/heads/omap4-for-tony
 
  My boot log:
  http://paste.ubuntu.com/491645/
 
  [Ghorai] can you use this bootargs?
  setenv bootargs root=/dev/mmcblk0p2 rw rootwait mem=463M
 console=ttyS2,115200n8
  And here is the log from my setup.
  [    2.493194] Waiting for root device /dev/mmcblk0p2...
  [    2.502960] mmc0: host does not support reading read-only switch.
 assuming write-enable.
  [    2.523895] mmc0: new high speed SDHC card at address e1ed
  [    2.531616] mmcblk0: mmc0:e1ed SD04G 3.75 GiB
  [    2.539550]  mmcblk0: p1 p2
  [    2.607360] EXT3-fs: barriers not enabled
 
  Using x-loader from
  http://gitorious.org/pandaboard/x-loader/commits/omap4_panda_L24.9 and
  upstream u-boot.
  [Ghorai] can you try with this x-loader
 
 https://docs.google.com/leaf?id=0B8fdjBBEQ4lDZGE3ZTBjNzEtOTQ0Ni00ZmFlLTlhO
 DgtN2QzNjUwMzBkNDI2hl=en
  In the mean time I will try with yours!

 I'm unable to boot with your x-loader at my ES2.0 (6 and 8 layers),
 however I'm able to boot it with ES1. Are you sure you're testing it
 at an ES2 board?

 This is what I get, it just hangs:
 Texas Instruments X-Loader 1.41 (Aug 11 2010 - 10:51:13)
 Could not read bootloader!
 X-Loader hangs
 [Ghorai] format the card and copy MLo and followed by u-boot, uImage
 And yes I am using EX 2.0 6-layer board.


 Cheers,
 --
 Ricardo Salveti de Araujo


I also tried Santosh's patches on my ES2.0 8 layers board. It's the
same as Ricardo:
http://pastebin.ubuntu.com/493938/

And Ghorai, I got the same error as Ricardo when I'm trying your MLO.

Thanks,
-Bryan
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-13 Thread Ghorai, Sukumar


[snip]
  
   [Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3,
 4430
  ES2.0 SDP, Blaze and Panda and all booting fine.
  
   And omap_4430sdp_defconfig also ok omap4.
 
  Which Panda version are you using during your tests? I tried
  omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and I'm
  unable to detect the MMC.
 
  Do I need any other patch to make the MMC work with Panda?
  [Ghorai] I have tested based on following tree/branch and using ES2.0
 PANDA only. Can you share bootlog enabling mmc/sd debug message?
  http://dev.omapzoom.org/?p=santosh/kernel-omap4-
 base.git;a=shortlog;h=refs/heads/omap4-for-tony
 
 My boot log:
 http://paste.ubuntu.com/491645/
 
[Ghorai] can you use this bootargs?
setenv bootargs root=/dev/mmcblk0p2 rw rootwait mem=463M console=ttyS2,115200n8
And here is the log from my setup.
[2.493194] Waiting for root device /dev/mmcblk0p2...
[2.502960] mmc0: host does not support reading read-only switch. assuming 
write-enable.
[2.523895] mmc0: new high speed SDHC card at address e1ed
[2.531616] mmcblk0: mmc0:e1ed SD04G 3.75 GiB
[2.539550]  mmcblk0: p1 p2
[2.607360] EXT3-fs: barriers not enabled

 Using x-loader from
 http://gitorious.org/pandaboard/x-loader/commits/omap4_panda_L24.9 and
 upstream u-boot.
[Ghorai] can you try with this x-loader
https://docs.google.com/leaf?id=0B8fdjBBEQ4lDZGE3ZTBjNzEtOTQ0Ni00ZmFlLTlhODgtN2QzNjUwMzBkNDI2hl=en
In the mean time I will try with yours!

 
 Cheers,
 --
 Ricardo Salveti de Araujo
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-13 Thread Ricardo Salveti
On Mon, Sep 13, 2010 at 12:06 PM, Ghorai, Sukumar s-gho...@ti.com wrote:
   [Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3,
 4430
  ES2.0 SDP, Blaze and Panda and all booting fine.
  
   And omap_4430sdp_defconfig also ok omap4.
 
  Which Panda version are you using during your tests? I tried
  omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and I'm
  unable to detect the MMC.
 
  Do I need any other patch to make the MMC work with Panda?
  [Ghorai] I have tested based on following tree/branch and using ES2.0
 PANDA only. Can you share bootlog enabling mmc/sd debug message?
  http://dev.omapzoom.org/?p=santosh/kernel-omap4-
 base.git;a=shortlog;h=refs/heads/omap4-for-tony

 My boot log:
 http://paste.ubuntu.com/491645/

 [Ghorai] can you use this bootargs?
 setenv bootargs root=/dev/mmcblk0p2 rw rootwait mem=463M 
 console=ttyS2,115200n8
 And here is the log from my setup.
 [    2.493194] Waiting for root device /dev/mmcblk0p2...
 [    2.502960] mmc0: host does not support reading read-only switch. assuming 
 write-enable.
 [    2.523895] mmc0: new high speed SDHC card at address e1ed
 [    2.531616] mmcblk0: mmc0:e1ed SD04G 3.75 GiB
 [    2.539550]  mmcblk0: p1 p2
 [    2.607360] EXT3-fs: barriers not enabled

 Using x-loader from
 http://gitorious.org/pandaboard/x-loader/commits/omap4_panda_L24.9 and
 upstream u-boot.
 [Ghorai] can you try with this x-loader
 https://docs.google.com/leaf?id=0B8fdjBBEQ4lDZGE3ZTBjNzEtOTQ0Ni00ZmFlLTlhODgtN2QzNjUwMzBkNDI2hl=en
 In the mean time I will try with yours!

I'm unable to boot with your x-loader at my ES2.0 (6 and 8 layers),
however I'm able to boot it with ES1. Are you sure you're testing it
at an ES2 board?

This is what I get, it just hangs:
Texas Instruments X-Loader 1.41 (Aug 11 2010 - 10:51:13)
Could not read bootloader!
X-Loader hangs

Cheers,
-- 
Ricardo Salveti de Araujo
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-13 Thread Ghorai, Sukumar


 -Original Message-
 From: Ricardo Salveti [mailto:rsalv...@rsalveti.net]
 Sent: Tuesday, September 14, 2010 12:22 AM
 To: Ghorai, Sukumar
 Cc: Shilimkar, Santosh; Kevin Hilman; linux-omap@vger.kernel.org;
 t...@atomide.com; Bryan Wu
 Subject: Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0
 
 On Mon, Sep 13, 2010 at 12:06 PM, Ghorai, Sukumar s-gho...@ti.com wrote:
[Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3,
  4430
   ES2.0 SDP, Blaze and Panda and all booting fine.
   
And omap_4430sdp_defconfig also ok omap4.
  
   Which Panda version are you using during your tests? I tried
   omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and
 I'm
   unable to detect the MMC.
  
   Do I need any other patch to make the MMC work with Panda?
   [Ghorai] I have tested based on following tree/branch and using ES2.0
  PANDA only. Can you share bootlog enabling mmc/sd debug message?
   http://dev.omapzoom.org/?p=santosh/kernel-omap4-
  base.git;a=shortlog;h=refs/heads/omap4-for-tony
 
  My boot log:
  http://paste.ubuntu.com/491645/
 
  [Ghorai] can you use this bootargs?
  setenv bootargs root=/dev/mmcblk0p2 rw rootwait mem=463M
 console=ttyS2,115200n8
  And here is the log from my setup.
  [    2.493194] Waiting for root device /dev/mmcblk0p2...
  [    2.502960] mmc0: host does not support reading read-only switch.
 assuming write-enable.
  [    2.523895] mmc0: new high speed SDHC card at address e1ed
  [    2.531616] mmcblk0: mmc0:e1ed SD04G 3.75 GiB
  [    2.539550]  mmcblk0: p1 p2
  [    2.607360] EXT3-fs: barriers not enabled
 
  Using x-loader from
  http://gitorious.org/pandaboard/x-loader/commits/omap4_panda_L24.9 and
  upstream u-boot.
  [Ghorai] can you try with this x-loader
 
 https://docs.google.com/leaf?id=0B8fdjBBEQ4lDZGE3ZTBjNzEtOTQ0Ni00ZmFlLTlhO
 DgtN2QzNjUwMzBkNDI2hl=en
  In the mean time I will try with yours!
 
 I'm unable to boot with your x-loader at my ES2.0 (6 and 8 layers),
 however I'm able to boot it with ES1. Are you sure you're testing it
 at an ES2 board?
 
 This is what I get, it just hangs:
 Texas Instruments X-Loader 1.41 (Aug 11 2010 - 10:51:13)
 Could not read bootloader!
 X-Loader hangs
[Ghorai] format the card and copy MLo and followed by u-boot, uImage
And yes I am using EX 2.0 6-layer board.

 
 Cheers,
 --
 Ricardo Salveti de Araujo
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-10 Thread Ghorai, Sukumar


 -Original Message-
 From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
 ow...@vger.kernel.org] On Behalf Of Shilimkar, Santosh
 Sent: Thursday, September 09, 2010 4:53 PM
 To: linux-omap@vger.kernel.org
 Cc: t...@atomide.com; khil...@deeprootsystems.com; Shilimkar, Santosh
 Subject: [PATCH 0/7] omap4: Fixes, hacks for es2.0
 
 This series has few fixes, hacks to get omap4 es2.0 working
 on mainline. The patches are generated against the mainline
 2.6.36-rc3.
 
 
 The series is boot tested tested on 4430 SDP, Blaze with
 omap_4430sdp_defconfig with file over NFS and MMC.
 
 Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
 SDPs. Same observation with Panda
 
 With omap3_defconfig, MMC while mounting the rootfs over MMC, the
 boot hangs. Same observation with Panda

[Ghorai] Santosh,
It's booing in another Panda. I think that's a board issue. 

 
 [5.794616] regulator_init_complete: incomplete constraints, leaving
 VUSIM on
 [5.802764] regulator_init_complete: incomplete constraints, leaving
 VPP on
 [5.816131] twl_rtc twl_rtc: setting system clock to 2000-01-01
 00:53:12 UTC (9  )
 [5.849304] mmc0: new high speed MMC card at address 0001
 [5.856323] mmcblk0: mmc0:0001 SEM08G 7.39 GiB
 [5.862091]  mmcblk0: unknown partition table
 [6.325500] omap_device: mmci-omap-hs.1: new worst case deactivate
 latency 0: 6
 [   18.424407] VFS: Cannot open root device mmcblk0p2 or unknown-
 block(179,2)
 [   18.431823] Please append a correct root= boot option; here are the
 available  ons:
 [   18.440643] b300 7757824 mmcblk0 driver: mmcblk
 [   18.446166] Kernel panic - not syncing: VFS: Unable to mount root fs on
 unknown
 
 All these patches are also available at:
   http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=summary
   head: omap4-for-tony
 
 David Anders (1):
   omap4: Panda: Add DEBUG_LL support
 
 Eric Dumazet (1):
   KS8851: Correct RX packet allocation
 
 Madhusudhan Chikkature (1):
   omap4: Workaround for CMD line reset.
 
 Santosh Shilimkar (4):
   omap4: Update id.c and cpu.h for es2.0
   omap4: Temporary fix silicon version detection
   omap4: l2x0: Fix init parameter for ES2.0
   omap4: Fix bootup crash observed with higher CPU clocks
 
  arch/arm/mach-omap2/id.c |   39
 +
  arch/arm/mach-omap2/omap4-common.c   |5 ++-
  arch/arm/plat-omap/dmtimer.c |2 +-
  arch/arm/plat-omap/include/plat/cpu.h|5 ++-
  arch/arm/plat-omap/include/plat/uncompress.h |1 +
  drivers/mmc/host/omap_hsmmc.c|8 +
  drivers/net/ks8851.c |   39 ++---
 -
  7 files changed, 71 insertions(+), 28 deletions(-)
 
 --
 To unsubscribe from this list: send the line unsubscribe linux-omap in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-10 Thread Ghorai, Sukumar


 -Original Message-
[..snip..]
  
The series is boot tested tested on 4430 SDP, Blaze with
omap_4430sdp_defconfig with file over NFS and MMC.
   
Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
SDPs. Same observation with Panda
   
With omap3_defconfig, MMC while mounting the rootfs over MMC, the
boot hangs. Same observation with Panda
  
   On my ES2.0 Panda, rootfs on MMC is now working with this series.
  
   I observed the same with MMC. Ramdisk boot worked for me on PANDA.
 
  Note that I said now working.  I think you read my message as not
  working.
 
 Yes I read it otherway ... Second time today :)
 
  IOW, rootfs on MMC *is* working for me on my es2.0 Panda.   I applied
  your series to current l-o master, and it works.
 
 Cool!!

[Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3, 4430 ES2.0 
SDP, Blaze and Panda and all booting fine.

And omap_4430sdp_defconfig also ok omap4.

 
   However, rootfs over NFS is not yet working, presumably because the
   OMAP4 EHCI support is needed for the USB-attached smsc95xx to work
   properly.
  
   This is correct. We need to get the MMC fixed o.w panda is unusable in
   it's current form.
  
  
[5.794616] regulator_init_complete: incomplete constraints,
  leaving
   VUSIM on
[5.802764] regulator_init_complete: incomplete constraints,
  leaving
   VPP on
[5.816131] twl_rtc twl_rtc: setting system clock to 2000-01-01
   00:53:12 UTC (9  )
[5.849304] mmc0: new high speed MMC card at address 0001
[5.856323] mmcblk0: mmc0:0001 SEM08G 7.39 GiB
[5.862091]  mmcblk0: unknown partition table
[6.325500] omap_device: mmci-omap-hs.1: new worst case
 deactivate
   latency 0: 6
  
   Based on this message, this is not a mainline kernel, but one where
 the
   omap_device conversion for MMC has been applied.
  
   This is mainline 2.6.36-rc3
   http://dev.omapzoom.org/?p=santosh/kernel-omap4-
  base.git;a=shortlog;h=refs/heads/omap4-for-tony

[..snip ..]
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-10 Thread Shilimkar, Santosh
 -Original Message-
 From: Ghorai, Sukumar
 Sent: Friday, September 10, 2010 4:00 PM
 To: Shilimkar, Santosh; Kevin Hilman
 Cc: linux-omap@vger.kernel.org; t...@atomide.com
 Subject: RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0
 
 
 
  -Original Message-
 [..snip..]
   
 The series is boot tested tested on 4430 SDP, Blaze with
 omap_4430sdp_defconfig with file over NFS and MMC.

 Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
 SDPs. Same observation with Panda

 With omap3_defconfig, MMC while mounting the rootfs over MMC, the
 boot hangs. Same observation with Panda
   
On my ES2.0 Panda, rootfs on MMC is now working with this series.
   
I observed the same with MMC. Ramdisk boot worked for me on PANDA.
  
   Note that I said now working.  I think you read my message as not
   working.
  
  Yes I read it otherway ... Second time today :)
 
   IOW, rootfs on MMC *is* working for me on my es2.0 Panda.   I applied
   your series to current l-o master, and it works.
  
  Cool!!
 
 [Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3, 4430
 ES2.0 SDP, Blaze and Panda and all booting fine.
 
 And omap_4430sdp_defconfig also ok omap4.
 
Thanks Sukumar!!
So with this testing data, the series works fine on 
all boards now with rootfs over MMC.

Regards,
Santosh
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-10 Thread Ricardo Salveti
On Fri, Sep 10, 2010 at 7:30 AM, Ghorai, Sukumar s-gho...@ti.com wrote:


 -Original Message-
 [..snip..]
  
The series is boot tested tested on 4430 SDP, Blaze with
omap_4430sdp_defconfig with file over NFS and MMC.
   
Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
SDPs. Same observation with Panda
   
With omap3_defconfig, MMC while mounting the rootfs over MMC, the
boot hangs. Same observation with Panda
  
   On my ES2.0 Panda, rootfs on MMC is now working with this series.
  
   I observed the same with MMC. Ramdisk boot worked for me on PANDA.
 
  Note that I said now working.  I think you read my message as not
  working.
 
 Yes I read it otherway ... Second time today :)

  IOW, rootfs on MMC *is* working for me on my es2.0 Panda.   I applied
  your series to current l-o master, and it works.
 
 Cool!!

 [Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3, 4430 ES2.0 
 SDP, Blaze and Panda and all booting fine.

 And omap_4430sdp_defconfig also ok omap4.

Which Panda version are you using during your tests? I tried
omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and I'm
unable to detect the MMC.

Do I need any other patch to make the MMC work with Panda?

Thanks,
-- 
Ricardo Salveti de Araujo
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-10 Thread Ghorai, Sukumar


 -Original Message-
 From: Ricardo Salveti [mailto:rsalv...@rsalveti.net]
 Sent: Friday, September 10, 2010 8:34 PM
 To: Ghorai, Sukumar
 Cc: Shilimkar, Santosh; Kevin Hilman; linux-omap@vger.kernel.org;
 t...@atomide.com
 Subject: Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0
 
 On Fri, Sep 10, 2010 at 7:30 AM, Ghorai, Sukumar s-gho...@ti.com wrote:
 
 
  -Original Message-
  [..snip..]
   
 The series is boot tested tested on 4430 SDP, Blaze with
 omap_4430sdp_defconfig with file over NFS and MMC.

 Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
 SDPs. Same observation with Panda

 With omap3_defconfig, MMC while mounting the rootfs over MMC,
 the
 boot hangs. Same observation with Panda
   
On my ES2.0 Panda, rootfs on MMC is now working with this series.
   
I observed the same with MMC. Ramdisk boot worked for me on PANDA.
  
   Note that I said now working.  I think you read my message as not
   working.
  
  Yes I read it otherway ... Second time today :)
 
   IOW, rootfs on MMC *is* working for me on my es2.0 Panda.   I applied
   your series to current l-o master, and it works.
  
  Cool!!
 
  [Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3, 4430
 ES2.0 SDP, Blaze and Panda and all booting fine.
 
  And omap_4430sdp_defconfig also ok omap4.
 
 Which Panda version are you using during your tests? I tried
 omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and I'm
 unable to detect the MMC.
 
 Do I need any other patch to make the MMC work with Panda?
[Ghorai] I have tested based on following tree/branch and using ES2.0 PANDA 
only. Can you share bootlog enabling mmc/sd debug message?
http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=shortlog;h=refs/heads/omap4-for-tony

 
 Thanks,
 --
 Ricardo Salveti de Araujo
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-10 Thread Shilimkar, Santosh
 -Original Message-
 From: Ricardo Salveti [mailto:rsalv...@rsalveti.net]
 Sent: Friday, September 10, 2010 8:34 PM
 To: Ghorai, Sukumar
 Cc: Shilimkar, Santosh; Kevin Hilman; linux-omap@vger.kernel.org;
 t...@atomide.com
 Subject: Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0
 
 On Fri, Sep 10, 2010 at 7:30 AM, Ghorai, Sukumar s-gho...@ti.com wrote:
 
 
  -Original Message-
  [..snip..]
   
 The series is boot tested tested on 4430 SDP, Blaze with
 omap_4430sdp_defconfig with file over NFS and MMC.

 Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
 SDPs. Same observation with Panda

 With omap3_defconfig, MMC while mounting the rootfs over MMC,
 the
 boot hangs. Same observation with Panda
   
On my ES2.0 Panda, rootfs on MMC is now working with this series.
   
I observed the same with MMC. Ramdisk boot worked for me on PANDA.
  
   Note that I said now working.  I think you read my message as not
   working.
  
  Yes I read it otherway ... Second time today :)
 
   IOW, rootfs on MMC *is* working for me on my es2.0 Panda.   I applied
   your series to current l-o master, and it works.
  
  Cool!!
 
  [Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3, 4430
 ES2.0 SDP, Blaze and Panda and all booting fine.
 
  And omap_4430sdp_defconfig also ok omap4.
 
 Which Panda version are you using during your tests? I tried
 omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and I'm
 unable to detect the MMC.
 
 Do I need any other patch to make the MMC work with Panda?
 
You don't need any more patches for kernel. Just use latest
Panda boot-loaders and it should work.

Regards,
Santosh


--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-10 Thread Ricardo Salveti
On Fri, Sep 10, 2010 at 12:09 PM, Ghorai, Sukumar s-gho...@ti.com wrote:
 -Original Message-
 On Fri, Sep 10, 2010 at 7:30 AM, Ghorai, Sukumar s-gho...@ti.com wrote:
  -Original Message-
  [..snip..]
 The series is boot tested tested on 4430 SDP, Blaze with
 omap_4430sdp_defconfig with file over NFS and MMC.

 Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
 SDPs. Same observation with Panda

 With omap3_defconfig, MMC while mounting the rootfs over MMC,
 the
 boot hangs. Same observation with Panda
   
On my ES2.0 Panda, rootfs on MMC is now working with this series.
   
I observed the same with MMC. Ramdisk boot worked for me on PANDA.
  
   Note that I said now working.  I think you read my message as not
   working.
  
  Yes I read it otherway ... Second time today :)
 
   IOW, rootfs on MMC *is* working for me on my es2.0 Panda.   I applied
   your series to current l-o master, and it works.
  
  Cool!!
 
  [Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3, 4430
 ES2.0 SDP, Blaze and Panda and all booting fine.
 
  And omap_4430sdp_defconfig also ok omap4.

 Which Panda version are you using during your tests? I tried
 omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and I'm
 unable to detect the MMC.

 Do I need any other patch to make the MMC work with Panda?
 [Ghorai] I have tested based on following tree/branch and using ES2.0 PANDA 
 only. Can you share bootlog enabling mmc/sd debug message?
 http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=shortlog;h=refs/heads/omap4-for-tony

My boot log:
http://paste.ubuntu.com/491645/

Using x-loader from
http://gitorious.org/pandaboard/x-loader/commits/omap4_panda_L24.9 and
upstream u-boot.

Cheers,
-- 
Ricardo Salveti de Araujo
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-09 Thread Kevin Hilman
Santosh Shilimkar santosh.shilim...@ti.com writes:

 This series has few fixes, hacks to get omap4 es2.0 working
 on mainline. The patches are generated against the mainline 
 2.6.36-rc3. 

Hi Santosh, thanks for this...

 The series is boot tested tested on 4430 SDP, Blaze with 
 omap_4430sdp_defconfig with file over NFS and MMC.

 Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
 SDPs. Same observation with Panda

 With omap3_defconfig, MMC while mounting the rootfs over MMC, the
 boot hangs. Same observation with Panda

On my ES2.0 Panda, rootfs on MMC is now working with this series.

However, rootfs over NFS is not yet working, presumably because the
OMAP4 EHCI support is needed for the USB-attached smsc95xx to work properly.

Kevin

 [5.794616] regulator_init_complete: incomplete constraints, leaving VUSIM 
 on
 [5.802764] regulator_init_complete: incomplete constraints, leaving VPP on
 [5.816131] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:53:12 
 UTC (9  )
 [5.849304] mmc0: new high speed MMC card at address 0001
 [5.856323] mmcblk0: mmc0:0001 SEM08G 7.39 GiB
 [5.862091]  mmcblk0: unknown partition table
 [6.325500] omap_device: mmci-omap-hs.1: new worst case deactivate latency 
 0: 6

Based on this message, this is not a mainline kernel, but one where the
omap_device conversion for MMC has been applied.

 [   18.424407] VFS: Cannot open root device mmcblk0p2 or 
 unknown-block(179,2)
 [   18.431823] Please append a correct root= boot option; here are the 
 available  ons:
 [   18.440643] b300 7757824 mmcblk0 driver: mmcblk
 [   18.446166] Kernel panic - not syncing: VFS: Unable to mount root fs on 
 unknown

 All these patches are also available at:
   http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=summary
   head: omap4-for-tony

 David Anders (1):
   omap4: Panda: Add DEBUG_LL support

 Eric Dumazet (1):
   KS8851: Correct RX packet allocation

 Madhusudhan Chikkature (1):
   omap4: Workaround for CMD line reset.

 Santosh Shilimkar (4):
   omap4: Update id.c and cpu.h for es2.0
   omap4: Temporary fix silicon version detection
   omap4: l2x0: Fix init parameter for ES2.0
   omap4: Fix bootup crash observed with higher CPU clocks

  arch/arm/mach-omap2/id.c |   39 +
  arch/arm/mach-omap2/omap4-common.c   |5 ++-
  arch/arm/plat-omap/dmtimer.c |2 +-
  arch/arm/plat-omap/include/plat/cpu.h|5 ++-
  arch/arm/plat-omap/include/plat/uncompress.h |1 +
  drivers/mmc/host/omap_hsmmc.c|8 +
  drivers/net/ks8851.c |   39 
 ++
  7 files changed, 71 insertions(+), 28 deletions(-)
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-09 Thread Shilimkar, Santosh
 -Original Message-
 From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
 Sent: Thursday, September 09, 2010 8:52 PM
 To: Shilimkar, Santosh
 Cc: linux-omap@vger.kernel.org; t...@atomide.com
 Subject: Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0
 
 Santosh Shilimkar santosh.shilim...@ti.com writes:
 
  This series has few fixes, hacks to get omap4 es2.0 working
  on mainline. The patches are generated against the mainline
  2.6.36-rc3.
 
 Hi Santosh, thanks for this...
 
  The series is boot tested tested on 4430 SDP, Blaze with
  omap_4430sdp_defconfig with file over NFS and MMC.
 
  Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
  SDPs. Same observation with Panda
 
  With omap3_defconfig, MMC while mounting the rootfs over MMC, the
  boot hangs. Same observation with Panda
 
 On my ES2.0 Panda, rootfs on MMC is now working with this series.

I observed the same with MMC. Ramdisk boot worked for me on PANDA.
 
 However, rootfs over NFS is not yet working, presumably because the
 OMAP4 EHCI support is needed for the USB-attached smsc95xx to work
 properly.

This is correct. We need to get the MMC fixed o.w panda is unusable in
it's current form.
 
 
  [5.794616] regulator_init_complete: incomplete constraints, leaving
 VUSIM on
  [5.802764] regulator_init_complete: incomplete constraints, leaving
 VPP on
  [5.816131] twl_rtc twl_rtc: setting system clock to 2000-01-01
 00:53:12 UTC (9  )
  [5.849304] mmc0: new high speed MMC card at address 0001
  [5.856323] mmcblk0: mmc0:0001 SEM08G 7.39 GiB
  [5.862091]  mmcblk0: unknown partition table
  [6.325500] omap_device: mmci-omap-hs.1: new worst case deactivate
 latency 0: 6
 
 Based on this message, this is not a mainline kernel, but one where the
 omap_device conversion for MMC has been applied.
 
This is mainline 2.6.36-rc3 
http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=shortlog;h=refs/heads/omap4-for-tony



--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0

2010-09-09 Thread Kevin Hilman
Shilimkar, Santosh santosh.shilim...@ti.com writes:

 -Original Message-
 From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
 Sent: Thursday, September 09, 2010 8:52 PM
 To: Shilimkar, Santosh
 Cc: linux-omap@vger.kernel.org; t...@atomide.com
 Subject: Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0
 
 Santosh Shilimkar santosh.shilim...@ti.com writes:
 
  This series has few fixes, hacks to get omap4 es2.0 working
  on mainline. The patches are generated against the mainline
  2.6.36-rc3.
 
 Hi Santosh, thanks for this...
 
  The series is boot tested tested on 4430 SDP, Blaze with
  omap_4430sdp_defconfig with file over NFS and MMC.
 
  Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
  SDPs. Same observation with Panda
 
  With omap3_defconfig, MMC while mounting the rootfs over MMC, the
  boot hangs. Same observation with Panda
 
 On my ES2.0 Panda, rootfs on MMC is now working with this series.

 I observed the same with MMC. Ramdisk boot worked for me on PANDA.

Note that I said now working.  I think you read my message as not
working.

IOW, rootfs on MMC *is* working for me on my es2.0 Panda.   I applied
your series to current l-o master, and it works.

 However, rootfs over NFS is not yet working, presumably because the
 OMAP4 EHCI support is needed for the USB-attached smsc95xx to work
 properly.

 This is correct. We need to get the MMC fixed o.w panda is unusable in
 it's current form.

 
  [5.794616] regulator_init_complete: incomplete constraints, leaving
 VUSIM on
  [5.802764] regulator_init_complete: incomplete constraints, leaving
 VPP on
  [5.816131] twl_rtc twl_rtc: setting system clock to 2000-01-01
 00:53:12 UTC (9  )
  [5.849304] mmc0: new high speed MMC card at address 0001
  [5.856323] mmcblk0: mmc0:0001 SEM08G 7.39 GiB
  [5.862091]  mmcblk0: unknown partition table
  [6.325500] omap_device: mmci-omap-hs.1: new worst case deactivate
 latency 0: 6
 
 Based on this message, this is not a mainline kernel, but one where the
 omap_device conversion for MMC has been applied.
 
 This is mainline 2.6.36-rc3 
 http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=shortlog;h=refs/heads/omap4-for-tony

Then I don't understand where the 'omap_device: mmci-omap-hs.1:...'
message is coming from in your kernel boot log.

It should not be present in a mainline kernel as the MMC conversion to
hwmod/omap_device is not in mainline, or linux-omap.

That's why I assumed your boot log excerpt came from an internal kernel
and not a mainline kernel.

Kevin
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html