I gave a try and here is the output:
boot> set linuxargs "root=/dev/mtdblock1 init=/linuxrc noinitrd
console=ttyS0,115200"
setting param <linuxargs> to value <root=/dev/mtdblock1 init=/linuxrc
noinitrd console=ttyS0,115200>
boot> set kernel_filename boot/zImage-2.6.7-hh0
setting param <kernel_filename> to value <boot/zImage-2.6.7-hh0>
boot> boot
booting jffs2...
booting boot/zImage-2.6.7-hh0 from partition >root<
Scanning all of flash for your JFFS2 convenience. Est Time: 6-12 seconds!
build_list: max = 01FBFFBC
....
dir entries = 00000E81
frag entries = 000042DF
+4 increments = 00000000
+file_offset increments = 00007F57
loaded file of size = 0x000C1C08 at location 0xA0008000
kernel partition base A0008000
kernel_magic=E1A00000
kernel_region_words[9]=016F2818
Linux ELF flash_imgstart=50040000 size=01FC0000 dest=A0000000
offset=00008000
MMU Control=00000079
MMU PIDVAM=00000000
Skipping kernel copy by request.
A0008000: E1A00000
A0008004: E1A00000
A0008008: E1A00000
A000800C: E1A00000
A0008010: E1A00000
A0008014: E1A00000
A0008018: E1A00000
A000801C: E1A00000
A0008020: EA000002
A0008024: 016F2818
root_filesystem_name=ramdisk
Grabbed linuxargs, argc = 00000001
Using mach_type 000000DC
setting boot parameters to
root=/dev/mtdblock1 init=/linuxrc noinitrd console=ttyS0,115200
Making core tag at A0000100
Making cmdline tag at A0000114
Making mem32 tag at A00001BC
command line is:
mtdparts=ipaq:0x00040000@0x00000000(bootldr)ro,0x01FC0000@0x00040000(root)
root=/dev/mt
dblock1 init=/linuxrc noinitrd console=ttyS0,115200
Disabling LCD controller
linuxEntryPoint=A0008000
Booting Linux image
Uncompressing
Linux....................................................... done,
booting the kernel
Then u do not get anything else...any idea????
Thanks
Telemaco
Jamey Hicks wrote:
> Telemaco Melia wrote:
>
>> Hi all there!
>>
>> I have been following in the last week the mailing list and I have
>> noticed somebody (few people :-( !!!) is working to get 2.6 kernels
>> running.
>> In the framework of the IST project Daidalos (www.ist-daidalos.org)
>> the ipaq is THE mobile device.
>> Within the consortium has been decided to go for 2.6 kernels since
>> the project will last for the next 2/3 years.
>> All the software will be develloped on top of these devices.
>> As you can understand we are REALLY interested to give you support in
>> testing and reporting bugs.
>> Unfortunately we cannot effort the development phase.
>> Is there any way to proceed faster with the 2.6 porting?
>
>
> I'm sure there are people who could find more time to work on 2.6
> porting if there were some funding available.
>
>> I have started this morning with the compilation of the latest cvs
>> snapshot...attached the log file.
>>
> Make sure to use a new enough toolchain. We've been using this 3.3.2
> cross toolchain that I built last fall:
>
> ftp://ftp.handhelds.org/pub/linux/arm/toolchain/arm-linux-gcc-3.3.2.tar.bz2
>
>
> -Jamey
>
>
>
-- Telemaco Melia telemaco.melia@netlab.nec.de Research Staff Member Tel: +49 (0) 6221 90511-42 Network Laboratories Fax: +49 (0) 6221 90511-55 NEC Europe Ltd. Web: http://www.netlab.nec.de Kurfrsten-Anlage 36 D-69115 Heidelberg GermanyReceived on Fri Jul 9 07:24:35 2004
This archive was generated by hypermail 2.1.8 : Fri Jul 09 2004 - 07:30:55 EDT