This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Config keys
- From: "David Marqvar (DAM)" <DAM at tt dot dk>
- To: "'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
- Date: Tue, 24 Jun 2003 16:38:37 +0200
- Subject: [ECOS] Config keys
Hi,
Is there any good reason that the config keys for serial devices are
serial-specific, e.g.:
#define CYG_IO_GET_CONFIG_SERIAL_INPUT_FLUSH 0x0104
could be defined as:
#define CYG_IO_GET_CONFIG_SERIAL_INPUT_FLUSH
CYG_IO_GET_CONFIG_INPUT_FLUSH
and the generic part should then be expanded with
// ======== 0x1000 Generic
===================================================
// Get/Set configuration 'key' values that can apply to more than one
// class of device.
#define CYG_IO_GET_CONFIG_INPUT_FLUSH 0x1104
... and so on.
This would allow different serial-alike devices to be handled in a common
way by upper layer applications.
In our development we both have serial devices as UART and USB (acting as a
serial device). Others may come, for example serial Bluetooth...
I can file a patch.... :-)
/David Marqvar
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss