Thanks Mika ...
Ur Conf file works ... Thanks for the help
Amit
--- In "amitaryan_king4ever" <>
wrote:
>
> Dear Mika
> The oops log of failure is :
>
> Uncompressing Linux... done, booting the kernel.
>
> Linux version 2.6.34 (gcc version 4.2.3) #2 PREEMPT Fri
> Jun 0
> CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
>
> CPU: VIVT data cache, VIVT instruction cache
>
> Machine: Technologic Systems TS-72xx SBC
>
> Memory policy: ECC disabled, Data cache writeback
>
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8016
>
> Kernel command line: console=ttyAM0,115200 root=/dev/mtdblock1 init=/linuxrc
>
> PID hash table entries: 128 (order: -3, 512 bytes)
>
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
>
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
>
> Memory: 8MB 8MB 8MB 8MB = 32MB total
>
> Memory: 29080k/29080k available, 3688k reserved, 0K highmem
>
> Virtual kernel memory layout:
>
> vector : 0xffff0000 - 0xffff1000 ( 4 kB)
>
> fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
>
> DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
>
> vmalloc : 0xc6000000 - 0xfe800000 ( 904 MB)
>
> lowmem : 0xc0000000 - 0xc5800000 ( 88 MB)
>
> modules : 0xbf000000 - 0xc0000000 ( 16 MB)
>
> .init : 0xc0008000 - 0xc0023000 ( 108 kB)
>
> .text : 0xc0023000 - 0xc0319000 (3032 kB)
>
> .data : 0xc031a000 - 0xc033ec40 ( 148 kB)
>
> Hierarchical RCU implementation.
>
> RCU-based detection of stalled CPUs is enabled.
>
> NR_IRQS:120
>
> VIC @fefb0000: id 0x00041190, vendor 0x41
>
> VIC @fefc0000: id 0x00041190, vendor 0x41
>
> Console: colour dummy device 80x30
>
> Calibrating delay loop... 99.73 BogoMIPS (lpj=498688)
>
> Mount-cache hash table entries: 512
>
> CPU: Testing write buffer coherency: ok
>
> NET: Registered protocol family 16
>
> ep93xx clock: PLL1 running at 400 MHz, PLL2 at 192 MHz
>
> ep93xx clock: FCLK 200 MHz, HCLK 100 MHz, PCLK 50 MHz
>
> ep93xx dma_m2p: M2P DMA subsystem initialized
>
> bio: create slab <bio-0> at 0
>
> SCSI subsystem initialized
>
> usbcore: registered new interface driver usbfs
>
> usbcore: registered new interface driver hub
>
> usbcore: registered new device driver usb
>
> NET: Registered protocol family 2
>
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
>
> TCP established hash table entries: 1024 (order: 1, 8192 bytes)
>
> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
>
> TCP: Hash tables configured (established 1024 bind 1024)
>
> 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)
>
> JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
>
> msgmni has been set to 56
>
> alg: No test for stdrng (krng)
>
> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
>
> io scheduler noop registered
>
> io scheduler deadline registered (default)
>
> Serial: AMBA driver
>
> apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
>
> console [ttyAM0] enabled
>
> apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
>
> apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
>
> brd: module loaded
>
> loop: module loaded
>
> Searching for NAND flash...
>
> NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V
> 8-bi)
> Scanning device for bad blocks
>
> Bad eraseblock 1483 at 0x00000172c000
>
> cmdlinepart partition parsing not available
>
> Using static partition definition
>
> Creating 3 MTD partitions on "ts7250-nand":
>
> 0x000000000000-0x000000004000 : "TS-BOOTROM"
>
> 0x000000004000-0x000001d04000 : "Linux"
>
> 0x000001d04000-0x000002000000 : "RedBoot"
>
> tun: Universal TUN/TAP device driver, 1.6
>
> tun: (C) 1999-2004 Max Krasnyansky <>
> ep93xx-eth version 0.1 loading
>
> eth0: ep93xx on-chip ethernet, IRQ 39, 00:d0:69:41:51:8d
>
> ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
>
> ep93xx-ohci ep93xx-ohci: EP93xx OHCI
>
> ep93xx-ohci ep93xx-ohci: new USB bus registered, assigned bus number 1
>
> ep93xx-ohci ep93xx-ohci: irq 56, io mem 0x80020000
>
> usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
>
> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
>
> usb usb1: Product: EP93xx OHCI
>
> usb usb1: Manufacturer: Linux 2.6.34 ohci_hcd
>
> usb usb1: SerialNumber: ep93xx
>
> hub 1-0:1.0: USB hub found
>
> hub 1-0:1.0: 3 ports detected
>
> Initializing USB Mass Storage driver...
>
> usbcore: registered new interface driver usb-storage
>
> USB Mass Storage support registered.
>
> mice: PS/2 mouse device common for all mice
>
> ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx-rtc as rtc0
>
> rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc1
>
> rtc-m48t86 rtc-m48t86: battery ok
>
> ep93xx_wdt: EP93XX watchdog, driver version 0.3
>
> usbcore: registered new interface driver usbhid
>
> usbhid: USB HID core driver
>
> TCP cubic registered
>
> NET: Registered protocol family 17
>
> NET: Registered protocol family 15
>
> ep93xx-rtc ep93xx-rtc: setting system clock to 1970-01-01 00:03:04 UTC (184)
>
> List of all partitions:
>
> 1f00 16 mtdblock0 (driver?)
>
> 1f01 29696 mtdblock1 (driver?)
>
> 1f02 3056 mtdblock2 (driver?)
>
> No filesystem could mount root, tried: ext3 ext2 vfat msdos
>
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(31,1)
>
> I am using the Driver for Cirrus Logic EP93xx SPI controller which is perhaps
> written by you.
> I am following: booting a linux kernel 2.6.34 inside the running kernel
> 2.4.26 using the bootloader.o utility.
>
> I don't knw wat is goin wrong ....
> Is booting the 2.6 kernel inside the 2.4 kernel is the only way or Is there
> any alternative way I could directly boot the new kernel ??
> Can u provide me the .config file for the .35 rc-kernel(with spi enabled ) .
> may be that could help
>
> regards
> Amit
>
>
>
> --- In Mika Westerberg <mika.westerberg@> wrote:
> >
> > Hi,
> >
> > On Mon, Jun 07, 2010 at 10:36:10AM -0000, amitaryan_king4ever wrote:
> > > I am using TS-7260 board for my data acquisition project.I need to use
> > > the spi pins on the board. But there is no native support for the spi
> > > driver in the 2.4.... kernel (native kernel shipped wid product).
> > >
> > > I compiled new kernel 2.6.34 with spi driver and it was successful . The
> > > company guys have provided everything on the SD card with the first
> > > parition of unknown type and wen i tried to DD there it was panic ...
> >
> > Can you provide the OOPS log of the failure? Also what SPI driver
> > are you using, the one provided by Cirrus Logic or the one that is
> > included in .35-rc1?
> >
> > > Next i tried with the procedure to boot kernel 2.6.34 inside 2.4.26ts ...
> > > through the bootloader utility. there also it is giving me errors of
> > > msg was :
> > > List of all partitions:
> > >
> > > 1f00 16 mtdblock0 (driver?)
> > >
> > > 1f01 29696 mtdblock1 (driver?)
> > >
> > > 1f02 3056 mtdblock2 (driver?)
> > >
> > > No filesystem could mount root, tried: ext3 ext2 vfat msdos
> > >
> > > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > > unknown-block(31,1)
> >
> > From here, it can be seen that there are no mmcblock partitions
> > available. But without full log it is hard to see what went wrong.
> >
> > > I need some help on this matter . My prime focus is to use spi on this
> > > device ...
> >
> > I've been using SPI on TS-7620 with 2.6.35-rc kernel (and before)
> > and it works (at least in my setup).
> >
> > Regards,
> > MW
> >
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|