public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Paul J THACKER <paul.thacker@st.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: How do I add a serial driver?
Date: Wed, 11 Jun 2008 17:32:00 -0000	[thread overview]
Message-ID: <48500CA7.3080201@st.com> (raw)
In-Reply-To: <20080611164820.GA523@lunn.ch>

Andrew Lunn wrote:

> So you need to look at your configuration and work out why your serial
> driver package is not active.
> 
> eg the top of the AT91 driver has:
> 
> cdl_package CYGPKG_IO_SERIAL_ARM_AT91 {
>     display       "Atmel AT91 serial device drivers"
> 
>     parent        CYGPKG_IO_SERIAL_DEVICES
>     active_if     CYGPKG_IO_SERIAL
>     active_if     CYGPKG_HAL_ARM_AT91

cdl_package CYGPKG_IO_SERIAL_ARM_CARTESIO {
     display       "Cartesio serial device drivers"

     parent        CYGPKG_IO_SERIAL_DEVICES
     active_if     CYGPKG_IO_SERIAL
     active_if     CYGPKG_HAL_ARM_CARTESIO

     requires      CYGPKG_ERROR
     include_dir   cyg/io
     include_files ; # none _exported_ whatsoever
     description   "
            This option enables the serial device drivers for the
            Cartesio."

     compile       -library=libextras.a   cartesio_serial.c

     define_proc {
         puts $::cdl_system_header "/***** serial driver proc output 
start *****/"
         puts $::cdl_system_header "#define 
CYGDAT_IO_SERIAL_DEVICE_HEADER <pkgconf/io_serial_arm_cartesio.h>"
         puts $::cdl_system_header "/*****  serial driver proc output 
end  *****/"
     }

> 
> We know you have CYGPKG_IO_SERIAL_DEVICES enabled. Does your
> configuration have CYGPKG_IO_SERIAL enabled? 

Not sure how to tell. It doesn't say one way or the other in configtool.

Does your package still
> require CYGPKG_HAL_ARM_AT91 which is not true for your hardware? Have
> you made a typo in the name of the replacement?

Don't think so. I've looked it over pretty carefully.
> 
> Look at your ecos.ecc file. You can learn a lot from that.

Don't have an ecos.ecc. Do you mean ecos.db?

> 
>     Andrew

Thanks,
Paul

  reply	other threads:[~2008-06-11 17:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 20:28 Paul J THACKER
2008-06-10 21:46 ` Andrew Lunn
2008-06-10 22:11   ` Paul J THACKER
2008-06-11  6:55     ` Andrew Lunn
2008-06-11 16:26       ` Paul J THACKER
2008-06-11 16:48         ` Andrew Lunn
2008-06-11 17:32           ` Paul J THACKER [this message]
2008-06-11 19:23             ` Andrew Lunn
2008-06-11 21:21               ` Paul J THACKER
2008-06-11 21:25                 ` Andrew Lunn
2008-06-11 21:29                   ` Paul J THACKER
2008-06-11 23:14                     ` Gary Thomas
     [not found]                       ` <48506034.30601@st.com>
2008-06-11 23:34                         ` Gary Thomas
2008-06-11 23:45                           ` Paul J THACKER
2008-06-12 11:11                             ` Gary Thomas
2008-06-12 16:35                               ` Paul J THACKER

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=48500CA7.3080201@st.com \
    --to=paul.thacker@st.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-devel@ecos.sourceware.org \
    /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).