This is the mail archive of the ecos-patches@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1001428] Hal bits for Kinetis K40 SLCD controller


Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001428

--- Comment #4 from Tomas Frydrych <tf+bugs.ecos@r-finger.com> 2011-12-21 18:33:30 GMT ---
(In reply to comment #3)
> Being on-chip doesn't change the relation, it's still a peripheral. The same
> device may be present on MCUs with different CPU architecture (esp. at
> Freescale). Also the division is reflected in eCos tree where we have hal and
> devs subtrees.

OK. So in the case of the K40 SLCD controller, where would you suggest to place
this? Looking at the eth/uart drivers, perhaps along the lines of
/dev/slcd/freescale/<something>, but I am not sure what identifier to assign to
this actual device.

> It's true that under devs subtree you  can find "architectural" directories
> such as arm and cortexm, etc. This is less problem for devices from
> manufacturers that support single architecture but still may lead us to a
> situation (there are examples) where some MCU has a choice between borrowing
> devices from "other architecture" or cloning them. I am trying to avoid this
> with Freescale for reasons stated earlier. I think it should not be difficult
> for us as we are just at the beginning with Kinetis.

Makes sense.

-- 
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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]