From: luo.jinhua <luo.jinhua@gd-linux.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Port U-Boot to SBC-2410X
Date: Thu, 1 Sep 2005 09:40:07 +0800 [thread overview]
Message-ID: <20050901013832.M94847@gd-linux.com> (raw)
In-Reply-To: <20050831151911.3DA5635265F@atlas.denx.de>
Thank for your reply.
I am sorry that I make some confusion between "xterm" and "shell" (By the way,
my english is so poor). In fact, hush in U-Boot calls function "readline"
(like that bash may use GNU readline library) to handle I/O and implement
terminal-extension, right? While terminal (usually serial driver in U-Boot) is
a minimal subset to drive I/O devices, readline can do more like command
history expansion and cmdline editing. My patch just modifys "readline"
function to use vivi's extension codes, which also means that it just consider
one line not a complete hush sentence (like "if...then...fi") as one history
item. However, I think, it is useful enough.
About the nand subsystem, I am glad to hear that there exists one fresh driver
branch. It makes sense to every user, I think. Because nor flash always works
as BOOT rom, while nand flash always works as DATA rom. In my embedded
project, I cannot do anything without a usable nand driver because the nor
flash chip is 1MB while the nand flash chip is 64MB on my board. Where to
place my kernel and the huge root filesystem? :-)
I will submit the three patches soon.
Best regards,
luo.jinhua
prev parent reply other threads:[~2005-09-01 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 13:55 [U-Boot-Users] Port U-Boot to SBC-2410X luo.jinhua
2005-08-31 15:19 ` Wolfgang Denk
2005-08-31 21:21 ` [U-Boot-Users] NAND support [was: Port U-Boot to SBC-2410X] Ladislav Michl
2005-08-31 23:05 ` Wolfgang Denk
2005-09-01 8:21 ` Ladislav Michl
2005-09-01 1:40 ` luo.jinhua [this message]
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=20050901013832.M94847@gd-linux.com \
--to=luo.jinhua@gd-linux.com \
--cc=u-boot@lists.denx.de \
/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