From: Bart Veer <bartv@redhat.com>
To: grante@visi.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] CDL question
Date: Wed, 12 Apr 2000 09:36:00 -0000 [thread overview]
Message-ID: <200004121636.RAA30793@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <20000412111447.A1581@visi.com>
>>>>> "Grant" == Grant Edwards <grante@visi.com> writes:
>> You cannot change the default value of some option in another
>> package (for the time being anyway), manipulating package
>> configury like that breaks encapsulation.
>>
>> Instead your HAL package should use an appropriate requires
>> property, i.e.:
>>
>> cdl_package XXXPKG_HAL_ARM_WHATEVER {
>> ...
>> requires CYGHWR_HAL_ARM_BIGENDIAN
>> }
>>
>> The libcdl inference engine should sort this out pretty much
>> automatically, with no user intervention.
Grant> Cool, thanks. The "no user intervention" part was what I
Grant> hadn't figured out how to do.
Grant> I was using "requires CYGHWR_HAL_ARM_BIGENDIAN == 1", but
Grant> that didn't set the user value, it just warned you when you
Grant> did an "ecosconfig check".
I believe it should actually figure things out as soon as you do the
`ecosconfig new', unless you explicitly disable inference with
--no-resolve. If you look at the resulting ecos.ecc savefile, you
should see CYGHWR_HAL_ARM_BIGENDIAN with an inferred value, which
takes priority over the default value.
However, I have just spotted a problem in the inference engine code:
currently it will fail to trigger for "xxx == 1" if xxx is a boolean,
it will only trigger if xxx has a data part. If you rewrite it as
"requires CYGHWR_HAL_ARM_BIGENDIAN" then things should work better.
Unfortunately the inference engine does still need a fair bit of work,
but it was not worth holding up the release for that.
Bart
next prev parent reply other threads:[~2000-04-12 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-12 8:46 Grant Edwards
2000-04-12 9:02 ` Bart Veer
2000-04-12 9:15 ` Grant Edwards
2000-04-12 9:36 ` Bart Veer [this message]
2001-08-23 10:25 Trenton D. Adams
2001-08-23 10:39 ` Bart Veer
2006-08-01 2:37 Grant Edwards
2006-08-01 16:27 ` Andrew Lunn
2009-06-06 14:01 Sergei Gavrikov
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=200004121636.RAA30793@sheesh.cygnus.co.uk \
--to=bartv@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=grante@visi.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).