public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Bart Veer <bartv@ecoscentric.com>
Cc: munz@speag.ch,  ecos-devel@sourceware.org
Subject: Re: What is the reason to...
Date: Tue, 18 Nov 2008 17:16:00 -0000	[thread overview]
Message-ID: <4922F829.3070507@eCosCentric.com> (raw)
In-Reply-To: <pnr65rjp66.fsf@delenn.bartv.net>

Bart Veer wrote:
>>>>>> "Oliver" == oliver munz @ s p e a g <munz@speag.ch> writes:
> 
>     Oliver> mark CYGPKG_IO_SPI as HARDWARE?
>     Oliver> I think Generic SPI or I2C and so one should be loadable
>     Oliver> whitout an template. Can we change this?
> 
> The problem here is that other drivers such as the wallclock or
> dataflash are likely to depend on the SPI/I2C bus being available. On
> some platforms there may even be platform HAL dependencies on the bus.
> Now, by convention you can enable flash support on a given platform
> simply by e.g. "ecosconfig add flash" and everything sorts itself out.
> If the SPI or I2C bus driver was not automatically part of the
> configuration then that would stop working.
> 
> If you want the SPI or I2C support to be automatically available when
> needed, working within the limitations of current CDL, then the
> generic SPI or I2C packages have to be part of the target definition
> in ecos.db. That means they have to be hardware packages.

I've said this before and will just take the opportunity to say it again:
the 'hardware' attribute just gets in the way. You can't have packages in
the target definition that aren't 'hardware', and you can't add packages
which are marked as 'hardware', so there is a wholly artificial division
between packages.

I would prefer the whole 'hardware' attribute was dropped and give platform
developers, and application developers the ability to control their own
hardware configuration without having to edit repository files. It should
be possible for the HAL developers to list any driver packages appropriate
for their hardware in the target definition; and possible for app
developers to add/remove from that as needed. There's always been plug-in
modules, expansion buses etc., nevermind modern configurable hardware, so
assuming hardware is static seems archaic.

I suspect it has cost people more wasted time and confusion than it has
ever saved. I've had to jump through these hoops, and not seen any benefit.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine

  parent reply	other threads:[~2008-11-18 17:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 14:46 oliver munz @ s p e a g
2008-11-04 18:57 ` Bart Veer
2008-11-07 18:20   ` oliver munz @ s p e a g
2008-11-08 21:40     ` Gábor Török
2008-11-08 23:25       ` Oliver Munz @ SNR
2008-11-09 11:08         ` Gary Thomas
2008-11-09 13:52           ` Bart Veer
2008-11-09 13:46       ` Bart Veer
2008-11-09 15:34         ` Frank Pagliughi
2008-11-09 13:35     ` Bart Veer
2008-11-23 21:43     ` Bart Veer
2008-11-18 17:16   ` Jonathan Larmour [this message]
2008-11-18 18:39     ` Bart Veer
2008-11-18 18:45       ` Jonathan Larmour

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=4922F829.3070507@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=bartv@ecoscentric.com \
    --cc=ecos-devel@sourceware.org \
    --cc=munz@speag.ch \
    /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).