Re: [fare@tunes.org: Re: [jornada] Jornada 820]

Dear Linux ARM kernel hackers, dear Jornadans,

here is the current status of Linux support for the Jornada 820:

* I installed the 2001-01-25 arm toolchain beta from
        ftp://ftp.handhelds.org/pub/linux/arm/toolchain/beta/
 (is there anything more recent?)
 and the 2.4.18-rmk5 linux kernel from
        http://www.arm.linux.org.uk/developer/release-2.4.0.shtml

* I've just reserved MACH_TYPE_JORNADA820 177 for the jornada 820,
 and duplicated the 720 support files into 820 support files,
 removing support from the SA-1111 and Epson chipsets that I know
 aren't there, and configuring for FB_SA1101 instead.
 There is no way this caricature of 820 support could work,
 but at least it configures and compiles correctly.

* I tried booting it with hpcboot.exe from
        http://cvsweb.netbsd.org/bsdweb.cgi/syssrc/sys/arch/hpc/stand/binary/ARM/hpcboot.exe.uu
 to see if at least the bootloader was functional.
 It looks like it was, though I cannot tell what kind of adaptation
 it would require for linux to be booted by it (does anyone know?)

* hpcboot loaded my pseudo-kernel "correctly".
 Resulting bootlog.txt attached.

* Most interesting is that
 1) if I read the bootlog correctly,
  the 16MB RAM seems to be at physical address 0xc0000000
 2) the framebuffer is reported by hpcboot at (virtual?) addr 0x00000000,
  and seems to coincide with the place the kernel is loaded at:
  indeed, the framebuffer is garbled with code, and you can
  see what very much looks like the source for the penguin logo at
  what looks like (at least roughly) the same offset in the framebuffer
  and in the System.map.
        c0013a34 ? linux_logo_red

Questions:
* how can I determine what devices there are in the computer?

* I assume most devices are already supported, and only need
 proper glue code and configuration. But how can I tell?

* do hpcboot and linux follow a common interface, or do I need
 to modify one or the other so that they will cooperate properly?
 Is there any other bootloader that would solve this problem?
 [Next thing, I'll try CyaCE-YACH]

* In particular, is there anything special to do with respect
 to the framebuffer being at 0x00000000 and the kernel being
 loaded at the very same address?

* [we'll see about non-supported devices later.]

Notes:
* in case it might help, my machine has a NE2000 PCMCIA card
 as well as a serial cable, and a 32MB CF card.

* the HP backup&restore utility seems dysfunctional, so the machine
 is restored in an unstable state :-(

* all the files I use, their original URLs, etc., are archived at
        ftp://Samaris.tunes.org/jornada820/

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
[ TUNES project for a Free Reflective Computing System | http://tunes.org ]
Moderation in temper is always a virtue;
but moderation in principle is always a vice. - Thomas Paine