From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001428] Hal bits for Kinetis K40 SLCD controller
Date: Thu, 22 Dec 2011 10:03:00 -0000 [thread overview]
Message-ID: <20111222100313.BBB432F7800E@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001428-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001428
John Dallaway <john@dallaway.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |john@dallaway.org.uk
--- Comment #6 from John Dallaway <john@dallaway.org.uk> 2011-12-22 10:03:11 GMT ---
(In reply to comment #5)
> Provided that it doesn't fit in any of existing directories, I would create
> directory with general name such as lcd and for device name I would refer to
> Freescale docs. That would probably give devs/lcd/freescale/slcd .
>
> Note: I wonder if another tree level would be suitable/desirable such as:
> devs/gui/lcd/... Would anybody comment pse?
Using an "lcd" hierarchy for LCD segment displays would imply a separate
hierarchy for LED segment displays with similar controllers. I think a more
generic name is desirable.
Historically, support for simple devices with no corresponding I/O
infrastructure package has tended to be bundled with the relevant HAL package.
However, I do appreciate the desire for portability across architectures.
A few possibilities for consideration:
1) Introduce a hal/devs/ hierarchy for HAL-level device definitions which may
be required across multiple architectures. Accessed directly as if part of a
platform HAL or variant HAL package.
2) Introduce a devs/misc/ hierarchy for miscellaneous simple eCos devices with
no corresponding I/O layer. Accessed via eCos device lookup.
3) Create an I/O infrastructure package for segment displays.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-12-22 10:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 9:38 [Bug 1001428] New: " bugzilla-daemon
2011-12-21 11:03 ` [Bug 1001428] " bugzilla-daemon
2011-12-21 12:05 ` bugzilla-daemon
2011-12-21 17:55 ` bugzilla-daemon
2011-12-21 18:33 ` bugzilla-daemon
2011-12-22 8:01 ` bugzilla-daemon
2011-12-22 10:03 ` bugzilla-daemon [this message]
2011-12-23 8:08 ` bugzilla-daemon
2011-12-23 8:31 ` bugzilla-daemon
2011-12-23 9:23 ` bugzilla-daemon
2011-12-23 10:19 ` bugzilla-daemon
2012-01-11 11:25 ` bugzilla-daemon
2012-01-11 11:28 ` bugzilla-daemon
2012-01-11 11:33 ` bugzilla-daemon
2012-01-11 11:43 ` bugzilla-daemon
2012-01-11 11:44 ` bugzilla-daemon
2012-01-11 11:45 ` bugzilla-daemon
2012-03-26 16:10 ` bugzilla-daemon
2012-03-26 16:22 ` bugzilla-daemon
2012-03-30 15:02 ` bugzilla-daemon
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=20111222100313.BBB432F7800E@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@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).