public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
Cc: 'Jonathan Larmour' <jifl@eCosCentric.com>,
	'Gary Thomas' <gary@mlbassoc.com>,
	"Ecos-List (E-mail)" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] HAL macros and RTC
Date: Wed, 29 Jan 2003 18:53:00 -0000	[thread overview]
Message-ID: <m38yx398rh.fsf@balti.calivar.com> (raw)
In-Reply-To: <9F77D654ED40B74CA79E5A60B97A087B0423EC@sd-exchange.sdesigns.com>

Fabrice Gautier <Fabrice_Gautier@sdesigns.com> writes:

> 
> I dont know if the "on core timer" is always plugged into the same IRQ line
> for MIPS or PPC,

It is, it's part of the architecture definition.

> but thats not the case for me. I think we should have in
> the guide: 
> 
> "You only have to calculate and enter the proper CYGNUM_HAL_RTC_CONSTANTS
> definitions in the platform CDL file and define CYGNUM_HAL_INTERRUPT_RTC in
> [some include file]"

Good point, I'll take a look at doing that.

> 
> By the way shouldnt the interrupt be a CDL option like the other RTC related
> constants ?

Not really. The interrupt used is fixed by the hardware of the timer,
usually. If a particular platform provided several timers, and if the
HAL implementor chose to allow a choice, then indeed this value might
need to change along with the definitions of the HAL_CLOCK_*()
macros. 

-- 
Nick Garnett - eCos Kernel Architect
http://www.eCosCentric.com/


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

  reply	other threads:[~2003-01-29 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 10:50 Fabrice Gautier
2003-01-29 18:53 ` Nick Garnett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-28  4:07 Fabrice Gautier
2003-01-28  4:33 ` Jonathan Larmour
2003-01-28  1:13 Fabrice Gautier
2003-01-28  1:43 ` Gary Thomas

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=m38yx398rh.fsf@balti.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=Fabrice_Gautier@sdesigns.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary@mlbassoc.com \
    --cc=jifl@eCosCentric.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).