This is the mail archive of the ecos-devel@sources.redhat.com 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: Serial driver for ARM s3c4510


On Mittwoch, 22. Oktober 2003 16:40, Bart Veer wrote:
> Regarding something like CYGPRI_SER_TEST_SER_DEV, that is really a
> characteristic of the testing infrastructure. Turn it into a booldata,
> disabled by default. For manual testing the user should decide
> explicitly which port(s) should be tested, enable the option and set
> the value. For automated testing the testing infrastructure should be
> smart enough to know which port(s) are actually connected to something
> that can handle serial tests and manipulate the appropriate
> configuration options.

So I can do it like that:

cdl_component CYGPKG_IO_SERIAL_ARM_AIM711_16X5X_TESTING {
    display    "Testing parameters"
    flavor     bool
    calculated 1
    active_if  CYGPKG_IO_SERIAL_ARM_AIM711_16X5X_SERIAL0

    i {
        display       "Serial device used for testing"
        flavor        booldata
        default_value 0
        legal_values  { 0 CYGDAT_IO_SERIAL_ARM_AIM711_16X5X_SERIAL0_NAME }
    }

    define_proc {
        puts $::cdl_header "#define CYGPRI_SER_TEST_CRASH_ID \"arm16x5x\""
        puts $::cdl_header "#define CYGPRI_SER_TEST_TTY_DEV  \"/dev/tty2\""
    }
}

But what should I do with CYGPRI_SER_TEST_TTY_DEV? Although I think this is a 
general problem, because it wouldn't make sense to make  
CYGPRI_SER_TEST_SER_DEV configureable but not CYGPRI_SER_TEST_TTY_DEV.

Maybe it is also possible to have this in the serial io package

cdl_interface CYGINT_IO_SERIAL_TEST_DEV {
    display     "Serial testing device"
}

and cdl_option CYGPRI_SER_TEST_SER_DEV implements it if enabled?

Roland


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