From: Wolfgang Denk <wd@denx.de>
To: Eli Brin <elib@rokonet.co.il>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Access u-boot environment variables from Linux
Date: Mon, 14 Jul 2003 12:13:39 +0200 [thread overview]
Message-ID: <20030714101344.67427C6D82@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 14 Jul 2003 12:18:17 +0200." <75DF04AC5ED4D511A9810090273CB4163F5DE2@rokonet-e.rokonet.co.il>
Dear Eli,
in message <75DF04AC5ED4D511A9810090273CB4163F5DE2@rokonet-e.rokonet.co.il> you wrote:
>
> >Hardware Information Block which can be installed at offset
> >0x0003FFC0 in the first flash bank?
>
> Yes, but our final target will use 0x0003FF00, so we can have more
> space. We are making our target as compatible as possible to the
> TQM860L.
Well, if you move the address, you're breaking compatibility anyway.
Feel free to implement a proprietary solution that fits your needs.
> Perhaps, and probably, you are right. I will re-check/re-think. It
> looks easier to make changes on the SELF scripts. And it can be used
> on Linux version that do not support the ELDK rebuild from scratch.
Agreed.
> Anyway, my original problem is solved :) . I use the /tools/env, and
> perhaps later the MTD patch.
Fine.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
In C we had to code our own bugs, in C++ we can inherit them.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-14 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 10:18 Access u-boot environment variables from Linux Eli Brin
2003-07-14 10:13 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-14 9:05 Eli Brin
2003-07-14 8:41 ` Wolfgang Denk
2003-07-13 15:38 Eli Brin
2003-07-13 22:04 ` Wolfgang Denk
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=20030714101344.67427C6D82@atlas.denx.de \
--to=wd@denx.de \
--cc=elib@rokonet.co.il \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).