public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: flynn@lure.u-psud.fr
To: mtd@infradead.org
Subject: Booting Arcom SBC
Date: Tue, 9 Jan 2001 11:14:19 +0100	[thread overview]
Message-ID: <20010109111419.A21801@jupiter.lure.net> (raw)


Hello,

  I am attempting to adapt the sbc_mediagx flash booting code to a different Arcom card.
I also need to adapt it to allow booting bzImage kernels.  My understanding is that the only
difference between booting a bzImage and a zImage kernel is that the kernel code needs to
be loaded at 0x100000 instead of at 0x10000, the setup code going to the same location as 
for zImage and the loader also starts kernel execution at the same address.

  Now sbc_mediagx.c already seems to set the kernel load address correctly for a big kernel
so the only modification I thought necessary (a part of course from removing the error termination in
case of a big kernel) was to read the system size from the kernel image instead of assuming a
size of (512-10)k.  Since the C code is running under protected mode and as far as I can tell
the code and data segment descriptors have been set up to access the full 32 bit address space
I thought that the sbc_mediagx_copy_from function should work correctly with a target address
of 0x100000.

  Unfortunately when I do this the machine locks up.  A little investigation has lead me to see that
I appear to be able to read/write to addresses above 0x100000 without difficulty but as soon
as I try to write a significant amount of data to those addresses, say more than 64 bytes, the machine locks up.
The code works and launches the kernel if I use a zImage loading at 0x1000.

  Does anyone see anything obvious that might explain this behavior or have an idea about what might 
be going on ?  Any help would be greatly appreciated.

Gerard

-- 
Gerard FLYNN                 Tel : 33.01.64.46.82.46
LURE Departement Anneaux     Fax : 33.01.64.46.74.97
Centre Universitaire Paris-Sud  BP 34
91898 ORSAY FRANCE



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

                 reply	other threads:[~2001-01-09 10:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010109111419.A21801@jupiter.lure.net \
    --to=flynn@lure.u-psud.fr \
    --cc=mtd@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox