public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Sam Pham <anhmn@yahoo.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Creating UART driver
Date: Wed, 14 Apr 2004 13:49:00 -0000	[thread overview]
Message-ID: <m3oepuj4pm.fsf@miso.calivar.com> (raw)
In-Reply-To: <20040413214606.55061.qmail@web11808.mail.yahoo.com>

Sam Pham <anhmn@yahoo.com> writes:

> Hello,
> 
> I have a simlar task as mentioned in the the email
> below.  One thing I don't understand about its
> explaination is the last step: 
> 
> "Finally,
> create a new 'target' section in the database for the
> EB40A with your
> new driver package (since you cannot add hardware
> packages to an
> existing target with configtool)"
> 
> Why do we have to create a new 'target' section? 
> Can't we just adding new driver package into the
> exising 'target' section?

In the example the original serial drivers are being replaced with new
ones. Hence it is necessary to make a new target. If you just add the
new drivers to the existing target, then you will have both sets of
drivers present at the same time. If this is what you want you can do
it. Just make sure that the device names are distinct.

> 
> Also, after adding new driver package into the
> existing 'target' section, my .ecc file does not have
> -hardware or -template for this new package.  For
> example, CYGPKG_IO_SERIAL_GENERIC_16X5X stands alone
> by itself:


This I cannot help you with. Maybe there are some obscure rules about
when a package gets marked with -hardware here. Note that you need a
platform customization package to go with the 16X5X driver. The lack
of this may have something to do with it.

> 
>     hardware    pc ;
>     template    default ;
>     package -hardware CYGPKG_HAL_POWERPC current ;
>     package -hardware CYGPKG_HAL_POWERPC_MPC8xx
> current ;
>     package -hardware CYGPKG_HAL_POWERPC_ADDER current
> ;
>     package -hardware CYGPKG_HAL_QUICC current ;
>     package -template CYGPKG_HAL current ;
>     package -template CYGPKG_IO current ;
>     package -template CYGPKG_IO_SERIAL current ;
>     package CYGPKG_IO_SERIAL_GENERIC_16X5X current ;
> 
> Thanks.
> 

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2004-04-14  9:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 22:12 [ECOS] What to use instead of pipe? Konstantin Azarov
2004-04-14  7:28 ` [ECOS] Creating UART driver Sam Pham
2004-04-14 13:49   ` Nick Garnett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-11 13:37 eibach
2003-09-11 13:37 ` Gary Thomas
2003-09-11 13:37 ` Eric Doenges

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=m3oepuj4pm.fsf@miso.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=anhmn@yahoo.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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).