This is the mail archive of the mailing list for the eCos project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Bug 1000740] Public Domain Curses for eCos

On Tue, May 05, 2009 at 05:19:31PM +0100, wrote:
> John Dallaway <> changed:
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |ASSIGNED
>          Extra Info|---                         |REQUESTED
>      Ever Confirmed|0                           |1
> --- Comment #8 from John Dallaway <>  2009-05-05 17:19:30 ---
> So far, I have seen output from the "tuidemo" and "firework" demos. I can
> navigate the menus and the fireworks are recognisable.
> Sergei, correct operation of the demos seems to be dependent on resetting
> minicom between each demo. Otherwise, no output is observed. Have you seen this
> behaviour?
> I am using eCos target pc_i82559 and minicom in VT102 mode.

I used synth with ecosynthserial and olpce2294. I had not the same
issue. I ran minicom as `minicom -o -c on'. Then: "^A-T, A, C" for
colors. If you would have mercurial istalled...

AFAIR, I removed a non-blocking write from PDC_scr_open() then. Perhaps,
that is it. At the least in GNU nano is built with this package I can
press ^L to refresh screen.

Can you try the newest package?

hg clone
cd pdcurses4ecos

Steven Clugston did report that his target has a problem with those my

    cyg_io_get_config(handle, CYG_IO_GET_CONFIG_SERIAL_OUTPUT_DRAIN, NULL,

But, my target has not the same problem.

> A few comments so far:
> The following CDL options need CDL "description" strings and should be "flavor
> bool", not "flavor data":

Agreed. I'll fix it.

> I think it would be preferable (and more consistent with other eCos packages)
> to build the demo programs as eCos tests under the control of the
> CYGBLD_PDCURSES_DEMOS option. Something like this should work (untested):
>    display "PDCurses tests"
>    no_define
>    flavor data
>    calculated { CYGBLD_PDCURSES_DEMOS ? src/demos/xmas src/demos/... : "" }
>  }

At first, I had the same thought, but then I thought that in a future
there can be a real small tests begin itself from CYG_TEST_INIT etc.
Because the drivers can be different, e.g. the keyless devices (LCD
screens). etc. But it is not issue and I can arrange it as you suggest.

> Configure bugmail:
> ------- You are receiving this mail because: -------
> You are the QA contact for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]