From: John Dallaway <john@dallaway.org.uk>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: CDL question about CYGHWR_IO_FLASH_DEVICE
Date: Sat, 07 Nov 2009 12:00:00 -0000 [thread overview]
Message-ID: <4AF56154.5030901@dallaway.org.uk> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901E84942@mi8nycmail19.Mi8.com>
Hi Hartley
H Hartley Sweeten wrote:
> I'm trying to cleanup the ep93xx port that Brian Austin from
> Cirrus posted to the Bug Management System on 2009-04-10.
>
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000739
Great. Hopefully the copyright assignment will come through soon.
> I have it almost finished but I am getting a message during
> the build that I don't understand. I think this happens
> during one of the ecosconfig steps before the actual make.
> The message is:
>
> C CYGHWR_IO_FLASH_DEVICE, "requires" constraint not satisfied: CYGHWR_IO_FLASH_DEVICE >= 1
>
> I have checked the ecos.ecc file for CYGHWR_IO_FLASH_DEVICE
> and found this:
>
> # >
> # Hardware FLASH device drivers
> # This calculated option gives the number of flash devices
> # on the current platform. The generic flash support requires
> # at least one device.
> #
> cdl_interface CYGHWR_IO_FLASH_DEVICE {
> # Implemented by CYGPKG_DEVS_FLASH_EP93XX_28FXXX, active, disabled
> # Implemented by CYGPKG_DEVS_FLASH_EP93XX_AMD, active, disabled
> # Implemented by CYGPKG_DEVS_FLASH_STRATA, active, enabled
> # Implemented by CYGPKG_DEVS_FLASH_AMD_AM29XXXXX, inactive, enabled
> # Implemented by CYGPKG_DEVS_FLASH_INTEL_28FXXX, inactive, enabled
> # This value cannot be modified here.
> # Flavor: data
> # Current_value: 1
> # Requires: CYGHWR_IO_FLASH_DEVICE >= 1
> # CYGHWR_IO_FLASH_DEVICE == 1
> # --> 1
>
> # The following properties are affected by this value
> # interface CYGHWR_IO_FLASH_DEVICE
> # Requires: CYGHWR_IO_FLASH_DEVICE >= 1
> # option CYGSEM_IO_FLASH_VERIFY_PROGRAM
> # ActiveIf: CYGHWR_IO_FLASH_INDIRECT_READS < CYGHWR_IO_FLASH_DEVICE
> # component CYGPKG_REDBOOT_FLASH
> # ActiveIf: CYGHWR_IO_FLASH_DEVICE
> };
>
> It appears that the "requires" constraint should be ok. Am I
> missing something?
From visual inspection, the relevant logic appears to be:
CYGPKG_DEVS_FLASH_STRATA:
active_if CYGINT_DEVS_FLASH_STRATA_REQUIRED
CYGPKG_DEVS_FLASH_EDB93XX_STRATA:
default_value 0
requires CYGPKG_DEVS_FLASH_STRATA
implements CYGINT_DEVS_FLASH_STRATA_REQUIRED
Firstly, CYGPKG_DEVS_FLASH_STRATA is a hardware package and should
therefore be added to the edb93xx target definition in ecos.db. The
CYGINT_DEVS_FLASH_STRATA_REQUIRED interface will ensure that this
package is inactive if it is not needed.
You can then eliminate the "requires CYGPKG_DEVS_FLASH_STRATA"
constraint on CYGPKG_DEVS_FLASH_EDB93XX_STRATA.
Does this eliminate the unexpected CDL conflict?
John Dallaway
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-11-07 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 20:40 [ECOS] " H Hartley Sweeten
2009-11-07 12:00 ` John Dallaway [this message]
2009-11-09 22:07 ` [ECOS] " H Hartley Sweeten
2009-11-11 20:56 ` [ECOS] " John Dallaway
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=4AF56154.5030901@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=hartleys@visionengravers.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).