From: Balint Cristian <rezso@rdsor.ro>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: DOCBoot update
Date: Tue, 4 Jan 2005 16:01:17 +0200 [thread overview]
Message-ID: <200501041601.17638.rezso@rdsor.ro> (raw)
In-Reply-To: <1104846254.13016.293.camel@hades.cambridge.redhat.com>
On Tuesday 04 January 2005 15:44, you wrote:
> You'd probably do better to add DiskOnChip support to RedBoot.
Yes. right.
As the discution on this arised:
I have personaly an DoC Millenium Plus 32M on an xscale [the very only one ], i very wanted to add to openwice-jtag [hope you know the tool] the
flash/dump/read faclity directly via JTAG but is possible only if the driver is 16 bit clean [xscale use DoC in 16 bit mode at early boot time],
and to write/rewrite an redboot/brendnew bootloader for arm platform need to have a very handy tool to debug preferable via JTAG.
The jtag work flowless in 8 bit DoC HW mode [i acheive this by a patch using MTD old pieces of code not the nand one] but as the chiken-egg law says:
xscale/arm want 16 bit .... [so cant write/debug a bootloader code on arm :) its horribly painfull without access to DoC by JTAG]
---> and so on etc etc ---> i can use only the new _nand_ driver, as pointed out evryone on this list .......
But,
The new nand driver is still unsuported for 32DOCMilplus32.
That fact can be grepped in the source code.
So,
David, everyone pointed out that you are the "man" on this issue, can tell me please:
a) what can i do to make nand to work with my chip, assuming that i can convert DOC MilPlus 16 one, few hint enough for a small magic over the code.
b) have you some plan to do this, can help me ? [i am ready to test the code]
c) i ask stupid thing ? [please notify]
d) i speak/wrote terrible english. [please notify]
Thanks to evryone,
~cristian
next prev parent reply other threads:[~2005-01-04 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 18:53 DOCBoot update Dan Brown
2005-01-04 9:19 ` Balint Cristian
2005-01-04 13:42 ` Dan Brown
2005-01-04 13:44 ` David Woodhouse
2005-01-04 14:01 ` Balint Cristian [this message]
2005-01-04 14:31 ` David Woodhouse
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=200501041601.17638.rezso@rdsor.ro \
--to=rezso@rdsor.ro \
--cc=dwmw2@infradead.org \
--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