From: Joshua Wise <joshua@joshuawise.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [H2200-port] LAB - labmtd.c fixed, managed to boot a kernel on h2200 with LAB
Date: Tue, 28 Sep 2004 15:28:08 -0400 [thread overview]
Message-ID: <4159BB48.9040004@joshuawise.com> (raw)
In-Reply-To: <opse1g21zple1n2s@mail.tlt.hu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sorry, I screwed up here and forgot to cc: to linux-mtd. When replying,
please cc: to h2200-port@handhelds.org
| I fixed the labmtd.c for the h2200. If you check my CVS log I mentioned
| that
| the shamcop_nand module defines a static partition at
| 0x00000000-0x02000000.
Ah, I see. You added code to remove the partition that shamcop_nand
defined. Cool. I'm not sure that this is the right way to do this,
though. cc:ing to linux-mtd.
| The lab tried to define other partitions over this regardeness of the
| already
| defined one.
| Yesterday I committed a small change in the assembly part of the
| armboot module.
| Actually Joshua committed as I've seen. :) btw. Thanks Joshua.
Okay. I have some local diffs to armboot that get rid of the
get_mtd_partitions since it was not properly #ifdef'ed, and because it
was hardcoded to "ipaq:". CC'ing to MTD list also about that.
| Today I managed to boot a kernel via mtd driver as well as ymodem.
| So LAB is really booting a kernel now!
Excellent! For fun, try booting LAB from LAB. :) It should work (in
fact, I've tested it recently.)
Out of curiousity, what space on the MTD device are you using to store
your kernel?
joshua
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBWbtGPn9tWOqA4LMRAhQbAJ4kCg5QoqqPzWwTGTc5QwYPpwg9ZQCeJrrn
ba5HZZIuxW7QIeF0CYgV75Q=
=gl9+
-----END PGP SIGNATURE-----
parent reply other threads:[~2004-09-28 19:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <opse1g21zple1n2s@mail.tlt.hu>]
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=4159BB48.9040004@joshuawise.com \
--to=joshua@joshuawise.com \
--cc=linux-mtd@lists.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