From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] DUTS: missing pieces for a beginner
Date: Thu, 30 Jul 2009 18:42:49 +0200 [thread overview]
Message-ID: <m24osu86ly.fsf@ohwell.denx.de> (raw)
In-Reply-To: <200907301427.24610.niklaus.giger@member.fsf.org> (Niklaus Giger's message of "Thu, 30 Jul 2009 14:27:23 +0200")
Hi Niklaus,
> Thanks for your quick answer and I got a few steps further.
Excellent.
> First I created my own version of "connect" (see attached Ruby script).
>
> Now at least I can connect and it seems to work.
Right - if you only reimplement the methods that we use locally then you
should not need to touch anything basically. This boils down to
providing a "remote_power" and "connect" utility.
> I think that my config files don't get loaded (seen with -v and verify by
> putting "p_err "was in ngiger_uboot_context.tcl" into my files.
> Here is my snippet:
[...]
> And I am not good at hacking using TCL. I do most of my scripting in Ruby as
> it is one of the few languages I have a chance to read my old code and still
> understand it.
;)
> Is this a easy fix for you?
It seems like this is a good opportunity to work on this end of duts.
Looking at the code it was pretty clear that it could not work as
expected, so I started somewhat cleaning up around here and freshened my
memory on how this is supposed to work at all. So do a "git remote
update" on your git tree and pull in the latest changes...
In spite of what I wrote earlier - the whole 'configuration' stuff
pivots on config/configs.tcl. In here we have configuration
descriptions. The _default must be first and initializes all "slots"
which can be overriden in subsequent duts_configs.
So If you want to only swap in your operatios, do something in there
like:
duts_config {
cfg_device_ops "config/my_ops.tcl"
}
and provide the config/my_ops.tcl.
Sorry my previous answer were based on incorrect memories.
Cheers
Detlev
--
Indeed, the author firmly believes that the best serious work is also
good fun. We needn't apologize if we enjoy doing research.
-- Donald Knuth
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2009-07-30 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 6:32 [U-Boot] DUTS: missing pieces for a beginner Niklaus Giger
2009-07-30 7:07 ` Wolfgang Denk
2009-07-30 10:14 ` Detlev Zundel
2009-07-30 12:27 ` Niklaus Giger
2009-07-30 16:42 ` Detlev Zundel [this message]
2009-07-30 16:53 ` Detlev Zundel
2009-07-31 8:18 ` Niklaus Giger
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=m24osu86ly.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.