From: Andrew Lunn <andrew@lunn.ch>
To: Gregg Levine <gregg.drwho8@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Interesting problem surfaces after adding the basic IDE driver to a simple RedBoot configuration
Date: Sat, 29 Dec 2007 02:47:00 -0000 [thread overview]
Message-ID: <20071223082831.GD31181@lunn.ch> (raw)
In-Reply-To: <18d205ed0712222105y34c2cfe0id6dd5b6c98d3471a@mail.gmail.com>
On Sun, Dec 23, 2007 at 12:05:20AM -0500, Gregg Levine wrote:
> Hello!
> Here's a new one. And unrelated to my earlier messages. I created an
> ECC file based on the regular PC w/ networking via an Intel device,
> and then added the IDE driver. Finally I found and attempted to add
> the ECM for floppy support for RedBoot. This then surfaced on the
> output pane:
> /usr/local/anoncvs/ecos/packages/hal/i386/pc/current/misc/redboot_FLOPPY.ecm:
> error
> The savefile contains a cdl_option for an unknown option
> `CYGBLD_BUILD_REDBOOT'
> /usr/local/anoncvs/ecos/packages/hal/i386/pc/current/misc/redboot_FLOPPY.ecm:
> error
> The savefile contains a cdl_option for an unknown option
> `CYGSEM_REDBOOT_VALIDATE_USER_RAM_LOADS'
> /usr/local/anoncvs/ecos/packages/hal/i386/pc/current/misc/redboot_FLOPPY.ecm:
> error
> The savefile contains a cdl_option for an unknown option
> `CYGSEM_REDBOOT_BSP_SYSCALLS'
>
>
> Now the first time I made a release of Redboot but without that errant
> IDE one, and booted it off of a floppy, it complained about the issues
> related to the IDE functions. It maybe because the current target is
> significantly older then the ECOS pattern. Then again maybe not.
lunn@londo:~/eCos/work$ ecosconfig new pc_i82559 redboot
U CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
U CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK, new inferred value 0
lunn@londo:~/eCos/work$ ecosconfig add ide_disk
lunn@londo:~/eCos/work$ ecosconfig import ../anoncvs-clean/packages/hal/i386/pc/current/misc/redboot_FLOPPY.ecm
U CYGHWR_HAL_I386_FPU_SWITCH_LAZY, new inferred value 0
lunn@londo:~/eCos/work$ ecosconfig tree
lunn@londo:~/eCos/work$ make -s
headers finished
/home/lunn/eCos/anoncvs-clean/packages/hal/i386/arch/current/src/redboot_linux_exec.c: In function `do_exec':
/home/lunn/eCos/anoncvs-clean/packages/hal/i386/arch/current/src/redboot_linux_exec.c:261: warning: implicit declaration of function `cyg_hal_plf_screen_position'
/home/lunn/eCos/anoncvs-clean/packages/hal/common/current/src/hal_stub.c: In function `handle_exception_cleanup':
/home/lunn/eCos/anoncvs-clean/packages/hal/common/current/src/hal_stub.c:457: warning: comparison between pointer and integer
build finished
Builds for me. I guess you forgot to use the redboot template.
Andrew
--
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:[~2007-12-23 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 9:48 Gregg Levine
2007-12-29 2:47 ` Andrew Lunn [this message]
2007-12-29 3:51 ` Gregg Levine
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=20071223082831.GD31181@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gregg.drwho8@gmail.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).