Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Manish Lachwani <mlachwani@mvista.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH] TX4927 processor can support different speeds
Date: Mon, 24 Jan 2005 13:28:29 -0800	[thread overview]
Message-ID: <41F5687D.30802@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.61L.0501242107040.17587@blysk.ds.pg.gda.pl>

Maciej W. Rozycki wrote:

>On Mon, 24 Jan 2005, Manish Lachwani wrote:
>
>  
>
>>>>Why is this approach (in the patch) bad?
>>>>        
>>>>
>[...]
>  
>
>>>It's fragile because clock frequencies are changing faster in today's
>>>world of electronics than the weather in April.
>>>      
>>>
>[...]
>  
>
>>So? Can you be a little more clear?
>>    
>>
>
> Oh well, how can you assure a given binary will be booted on a CPU driven 
>by the right frequency?  Is the clock source inside the chip containing 
>the CPU at least?
>
>  Maciej
>
>  
>
Ok, that make things clear. Thanks Maciej,

Manish Lachwani

  reply	other threads:[~2005-01-24 21:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23 19:23 [PATCH] TX4927 processor can support different speeds Manish Lachwani
2005-01-23 19:41 ` Thiemo Seufer
2005-01-23 19:51   ` Ralf Baechle
2005-01-23 20:39     ` Manish Lachwani
2005-01-24 20:22       ` Ralf Baechle
2005-01-24 20:48         ` Manish Lachwani
2005-01-24 21:13           ` Maciej W. Rozycki
2005-01-24 21:28             ` Manish Lachwani [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-24 21:23 Brad Larson
2005-01-25  0:37 ` Maciej W. Rozycki

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=41F5687D.30802@mvista.com \
    --to=mlachwani@mvista.com \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=ralf@linux-mips.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