From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <openembedded-devel@lists.openembedded.org>
Subject: Re: [RFC] base_less_or_equal() for numerical value testing in OE
Date: Wed, 28 Feb 2007 00:07:12 +0200 [thread overview]
Message-ID: <1472918034.20070228000712@gmail.com> (raw)
In-Reply-To: <45E4A553.2060004@dominion.kabel.utwente.nl>
Hello Koen,
Tuesday, February 27, 2007, 11:40:35 PM, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Paul Sokolovsky schreef:
>> Well, that's good explanation from the point of view of birbake's
>> limitation we (still) have, but I'd like to approach from another side -
>> of what usecases we face. So, there was one case when
>> base_conditional() was used for checking ROM size too,
> Checking for ROM size is bogus, since you can't write to it anyway, and should be removed.
> I suspect you mean 'flash size'.
Sure. ROOT_FLASH_SIZE is the parameter being checked. And I hope
layman's using of "ROM" and "Flash" as synonyms won't confuse real pro's.
In particular, I hope that if a vendor with mask-ROM based design will
review OE as their software integration solution, the fact that the
parameter is called "ROOT_FLASH_SIZE", won't make them think they
can't be served by OE ;-).
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-02-27 22:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 20:35 [RFC] base_less_or_equal() for numerical value testing in OE Paul Sokolovsky
2007-02-27 20:38 ` Koen Kooi
2007-02-27 20:49 ` Paul Sokolovsky
2007-02-27 20:49 ` Richard Purdie
2007-02-27 21:31 ` Paul Sokolovsky
2007-02-27 21:40 ` Koen Kooi
2007-02-27 22:07 ` Paul Sokolovsky [this message]
2007-02-27 22:03 ` Richard Purdie
2007-03-04 23:30 ` Paul Sokolovsky
2007-03-04 23:40 ` Richard Purdie
2007-03-05 6:56 ` Koen Kooi
2007-03-05 8:12 ` Marcin Juszkiewicz
2007-03-05 10:07 ` Paul Sokolovsky
2007-03-05 9:33 ` Paul Sokolovsky
2007-02-28 13:09 ` Koen Kooi
2007-02-28 14:04 ` Philip Balister
2007-03-04 23:34 ` Paul Sokolovsky
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=1472918034.20070228000712@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.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