[iPAQ] Re: h3600 and kernel 2.6 (Prabhat Avasare)

I was actually working on porting 2.6 to the
31xx/36xx/37xx (they use a different technology to
connect to the peripherals which aren't directly tied
to the processor), but I got a little sidetracked.

Also, my 3650 appears to have become inoperable except
via A/C power (tried 2 different replacement batteries
w/ no luck), so some things -- like the battery driver
-- might be hard for me to test on other than my 3150.

Anyway, I'm planning on jumping back on this task
soon, I'll try to keep people on the various lists &
the wiki up-to-date w/ my progress.

Dave

P.S. -- If anyone knows whether it's possible/likely
that my battery issue is NOT a hardware problem (i.e.,
bootldr or kernel version are at fault), let me know
(bootldr is 2.20.1, kernel is 2.4.19-rmk6-pxa1-hh13)
--- Pierluigi Frullani <pierluigi.frullani@frumar.it>
wrote:
> > Subject: [Familiar] h3600 and kernel 2.6
> >> Has anyone has any success in getting a working
> 2.6 based kernel running
> >> on a h36xx, and if they have could i have a look
> at the .config file
> >
> > and did you have to change any kernel source code?
> > I had some partial success in that. Refer to the
> posting earlier -
> >
>
http://handhelds.org/hypermail/familiar/210/21077.html
> > regarding "trying to run kernel 2.6 on h3760".
> >
> I'm trying to compile 2.6.3-hh2 from cvs, but must
> say that it seems to be
> rather a hard task.
>
> I've tryied either make ipaqsa_defconfig then
> h3600_defconfig, but both
> need some tweek to config file.
> After having successfully compiled the kernel I've
> haved a couple of
> problems.
> The first one is easy to fix, as the console seems
> to be locked at 38400,
> and can be workarounded by using the console at
> 38400. You loose the
> first messages from bootloader, but you can happely
> see your fresh kernel
> panic :
>
> Linux version 2.6.3-hh2 (pigi@topolinux) (gcc
> version 3.3.2) #3 Wed Mar 31
> 00:08:11 CEST 2004
> CPU: StrongARM-1110 [6901b118] revision 8 (ARMv4)
> Machine: HP iPAQ H3600
> Memory policy: ECC disabled, Data cache writeback
> On node 0 totalpages: 8192
> DMA zone: 8192 pages, LIFO batch:2
> Normal zone: 0 pages, LIFO batch:1
> HighMem zone: 0 pages, LIFO batch:1
> Built 1 zonelists
> Kernel command line:
>
mtdparts=ipaq:0x00040000@0x00000000(bootldr)ro,0x00FC0000@0x00040000(root)
> root=/dev/mtdblock1 init=/linuxrc noinitrd con
> sole=none rootfstype=jffs2
> <7>Relocating machine vectors to 0xffff0000
> PID hash table entries: 256 (order 8: 2048 bytes)
> Console: colour dummy device 80x30
> <6>Memory: 32MB = 32MB total
> <5>Memory: 30536KB available (1380K code, 348K data,
> 80K init)
> Calibrating delay loop... 137.21 BogoMIPS
> <6>Dentry cache hash table entries: 4096 (order: 2,
> 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192
> bytes)
> Mount-cache hash table entries: 512 (order: 0, 4096
> bytes)
> <6>CPU: Testing write buffer coherency: ok
> POSIX conformance testing by UNIFIX
> <6>NET: Registered protocol family 16
> <6>Linux Kernel Card Services
> <6> options: none
> <1>Unable to handle kernel NULL pointer dereference
> at virtual address
> 00000018
> <1>pgd = c0004000
> <1>[00000018] *pgd=00000000
> Internal error: Oops: c0007005 [#1]
> CPU: 0
> PC is at sa1100fb_init_fbinfo+0xd4/0x280
> LR is at sa1100fb_get_machine_info+0x2c/0x74
> pc : [<c0013d80>] lr : [<c0013bf8>] Not
> tainted
> sp : c023dec8 ip : c023deb4 fp : c023def8
> r10: 003000ff r9 : ffffffff r8 : c019249c
> r7 : c0224000 r6 : c0186974 r5 : ffffffed r4 :
> c0186974
> r3 : c0191e60 r2 : 00410032 r1 : 00000000 r0 :
> 00000000
> Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment
> kernel
> Control: C000717F Table: C000717F DAC: 0000001D
> Process swapper (pid: 1, stack limit = 0xc023c104)
> Stack: (0xc023dec8 to 0xc023e000)
> dec0: c023ded4 c003a6f0 c0186974
> ffffffed c0186974 c0191ef0
> dee0: c019249c 00000000 00000000 c023df18 c023defc
> c0013f68 c0013cb8 c023df18
> df00: c0186974 ffffffed c0191ed8 c023df34 c023df1c
> c00e791c c0013f38 c018697c
> df20: c0191ed8 c01924f8 c023df50 c023df38 c00e7a20
> c00e78e0 c0192450 c0191ed8
> df40: 00000000 c023df74 c023df54 c00e7c60 c00e79e0
> 00000000 c001a630 00000009
> df60: c016161c c01c6560 c023df88 c023df78 c00e7f68
> c00e7bf8 00000000 c023dfa0
> df80: c023df8c c00137b8 c00e7f38 0010000b c01691ec
> c023dfc4 c023dfa4 c0011a88
> dfa0: c001372c c023c000 c001b398 00000000 c001b484
> 00000000 c023dfe4 c023dfc8
> dfc0: c0008768 c0011a00 00000000 00000000 00000000
> 00000000 c023dff4 c023dfe8
> dfe0: c001c0a0 c000872c 00000000 c023dff8 c0037d8c
> c001c084 00000000 00000000
> Backtrace:
> [<c0013cac>] (sa1100fb_init_fbinfo+0x0/0x280) from
> [<c0013f68>]
> (sa1100fb_probe+0x3c/0xfc)
> [<c0013f2c>] (sa1100fb_probe+0x0/0xfc) from
> [<c00e791c>]
> (bus_match+0x48/0x70)
> r6 = C0191ED8 r5 = FFFFFFED r4 = C0186974
> [<c00e78d4>] (bus_match+0x0/0x70) from [<c00e7a20>]
> (driver_attach+0x4c/0x80)
> r6 = C01924F8 r5 = C0191ED8 r4 = C018697C
> [<c00e79d4>] (driver_attach+0x0/0x80) from
> [<c00e7c60>]
> (bus_add_driver+0x74/0x84)
> r6 = 00000000 r5 = C0191ED8 r4 = C0192450
> [<c00e7bec>] (bus_add_driver+0x0/0x84) from
> [<c00e7f68>]
> (driver_register+0x3c/0x40)
> r8 = C01C6560 r7 = C016161C r6 = 00000009 r5 =
> C001A630
> r4 = 00000000
> [<c00e7f2c>] (driver_register+0x0/0x40) from
> [<c00137b8>]
> (fbmem_init+0x98/0xb8)
> [<c0013720>] (fbmem_init+0x0/0xb8) from [<c0011a88>]
> (chr_dev_init+0x94/0xb0)
> r5 = C01691EC r4 = 0010000B
> [<c00119f4>] (chr_dev_init+0x0/0xb0) from
> [<c0008768>]
> (do_initcalls+0x48/0xb8)
> r8 = 00000000 r7 = C001B484 r6 = 00000000 r5 =
> C001B398
> r4 = C023C000
> [<c0008720>] (do_initcalls+0x0/0xb8) from
> [<c001c0a0>] (init+0x28/0xc8)
> r7 = 00000000 r6 = 00000000 r5 = 00000000 r4 =
> 00000000
> [<c001c078>] (init+0x0/0xc8) from [<c0037d8c>]
> (do_exit+0x0/0x3a0)
> Code: e1a00007 e58731e0 ebffff93 e59fa194 (e5903018)
> <0>Kernel panic: Attempted to kill init!
>
> This is obviously a problem in sa1100fb_init_fbinfo
> but, being basically
> an assembler code, it's a bit far from my knowledge.
> I will try to backport the code from 2.4.19 as soon
> as I have time, but I
> don't think I will have more success.
>
> If anyone is interessed, we could try to unify the
> effort, as it seems
> that not a lot of people are interessed in an SA
> port for 2.6
>
> Pigi
>
> _______________________________________________
> The Familiar Linux Distribution
> Familiar mailing list
> Familiar@handhelds.org
> https://handhelds.org/mailman/listinfo/familiar
> irc://irc.freenode.net #familiar
>
Received on Wed Mar 31 23:38:53 2004