This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: Serial driver for ARM s3c4510
Roland Caßebohm wrote:
define_proc {
puts $::cdl_system_header "/** serial driver proc output start **/"
puts $::cdl_system_header "#ifndef CYGDAT_IO_SERIAL_DEVICE_HEADER"
puts $::cdl_system_header "#define CYGDAT_IO_SERIAL_DEVICE_HEADER
<pkgconf/io_serial_arm_aim711.h>"
puts $::cdl_system_header "#endif"
puts $::cdl_system_header "/** serial driver proc output end **/"
puts $::cdl_header "#include <pkgconf/system.h>";
puts $::cdl_header "#include <pkgconf/io_serial_arm_s3c4510.h>";
puts $::cdl_header "#include <pkgconf/io_serial_generic_16x5x.h>";
puts $::cdl_header "#include CYGDAT_IO_SERIAL_ARM_S3C4510_CFG";
puts $::cdl_header "#include CYGDAT_IO_SERIAL_GENERIC_16X5X_CFG";
}
}
Now both configurations are included in CYGDAT_IO_SERIAL_DEVICE_HEADER.
The cdl_option CYGPRI_SER_TEST_SER_DEV I have only implemented in one package
(aim711_16x5x), so there is no conflict. Maybe this could be made
congureable.
Hmm. It's very unlikely that a user would notice that only one serial
device was being tested, and being founded on completely different
drivers, that's quite unfortunate. Similarly automated testing
infrastructure wouldn't be able to manage either.
But if I do it like that, I have three directorys for AIM in devs/serial/arm
(aim711 aim_s3c4510 aim711_16x5x). Maybe I should make subdirectorys under
devs/arm/aim711? Or I however make it to only one package because it is only
one platform?
If there are to be three directories, then yes, make subdirectories under
an aim711 directory (although consider whether anything here might be
applicable to other AIM models, although probably not).
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine