public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] dynamic setting of CONFIG_SYS_CLK_FREQ
Date: Mon, 26 Apr 2004 09:33:44 +0300	[thread overview]
Message-ID: <408CAD48.4020004@intracom.gr> (raw)
In-Reply-To: <20040425140342.28300C109F@atlas.denx.de>

Wolfgang Denk wrote:

>In message <6A9BF178-9496-11D8-9316-000393DBC2E8@motorola.com> you wrote:
>
>>I realized that sys_clk is not defined, I was going to add it for 85xx 
>>since none of the other defines in gd currently represent the value. 
>>
>
>Do we really need this value? Please keep "gd"  free  from  redundand
>values,  i.  e. from data which can be derived/calculated easily from
>other variables.
>
>
>>The other option would be to have a function return the proper 
>>frequency (as suggested earlier in the thread). Any suggestions as to 
>>which option would be preferred?
>>
>
>The function approach sounds cleaner to me.
>
>
>Best regards,
>
>Wolfgang Denk
>
>
IMHO the gd data are pretty much useless in a complicated environment.

For example when you have multiple network interfaces you have no
information which network interface was used to obtain the configuration,
which was it's ethernet address etc.

For me the gd is usefull only for the simple case of most boards with
one network interface, fixed clock etc.

For anything more complicated is better to parse the environment variables.

Some information however is only available in the gd, for example the 
clocks.

Why don't we just add the missing information to the environment variables?

Regards

Pantelis

  reply	other threads:[~2004-04-26  6:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 16:02 [U-Boot-Users] dynamic setting of CONFIG_SYS_CLK_FREQ Kumar Gala
2004-04-22 17:14 ` Wolfgang Denk
2004-04-22 17:28   ` Kumar Gala
2004-04-22 19:44     ` Wolfgang Denk
2004-04-22 19:51       ` Kumar Gala
2004-04-25 14:03         ` Wolfgang Denk
2004-04-26  6:33           ` Pantelis Antoniou [this message]
2004-04-26  8:02             ` Wolfgang Denk
2004-04-26  8:16               ` Pantelis Antoniou
2004-04-26  9:14                 ` Wolfgang Denk
2004-04-26 10:18                   ` Pantelis Antoniou
2004-04-26 11:13                     ` Wolfgang Denk
2004-04-26 11:32                       ` Pantelis Antoniou
2004-04-26 13:03                         ` Wolfgang Denk
2004-04-26 13:25                           ` Pantelis Antoniou
2004-04-26 14:00                             ` Wolfgang Denk
2004-04-22 17:58 ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2004-04-22 17:52 VanBaren, Gerald

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=408CAD48.4020004@intracom.gr \
    --to=panto@intracom.gr \
    --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