From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] inka4x0: board specific RTC support.
Date: Thu, 11 Dec 2008 16:25:02 +0100 [thread overview]
Message-ID: <m2skouray9.fsf@ohwell.denx.de> (raw)
In-Reply-To: <20081209234110.774A6834B020@gemini.denx.de> (Wolfgang Denk's message of "Wed, 10 Dec 2008 00:41:10 +0100")
Hi Wolfgang,
> Dear ap at denx.de,
>
> In message <1227214731-19542-3-git-send-email-ap@denx.de> you wrote:
>> From: Andreas Pfefferle <ap@denx.de>
>>
>> This patch adds the board specific communication routines needed
>> by the external 4543 RTC.
>
> No, that's broken by design. An RTC is not board-dependent, but a
> generic piece of hardware. Code for it does not belong into any
> board-specific file, but into drivers/rtc/
Did you actually check what he does?
He does exactly what you request, he puts all the 4543 code into
drivers/rtc, but this cannot globally encode on how to access the chip
from a specific hardware. So he factored that out of the rtc driver
(correctly in my opinion) and has only this glue code in the board
files.
What *exactly* is broken by design in this approach?
Cheers
Detlev
--
FORTRAN's tragic fate has been its wide acceptance, mentally chaining thousands
and thousands of programmers to our past mistakes. I pray daily that more of my
fellow-programmers may find the means of freeing themselves from the curse of
compatibility. -- Edsger W. Dijkstra
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2008-12-11 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ap@denx.de>
2008-11-20 20:58 ` [U-Boot] [PATCH] Hardware diagnosis for inka4x0 boards ap at denx.de
2008-11-20 20:58 ` [U-Boot] [PATCH] =?utf-8?q?rtc:=20add=20support=20for=204543=20RTC=20(manufactured=20by=20e.g.=20EPSON) ap at denx.de
2008-11-20 20:58 ` [U-Boot] [PATCH] inka4x0: board specific RTC support ap at denx.de
2008-11-20 20:58 ` [U-Boot] [PATCH] inka4x0: hardware diagnosis and RTC ap at denx.de
2008-11-20 21:34 ` Jean-Christophe PLAGNIOL-VILLARD
2008-11-20 22:07 ` Wolfgang Denk
2008-12-09 23:39 ` Wolfgang Denk
2008-11-20 21:30 ` [U-Boot] [PATCH] inka4x0: board specific RTC support Jean-Christophe PLAGNIOL-VILLARD
2008-12-09 23:41 ` Wolfgang Denk
2008-12-11 15:25 ` Detlev Zundel [this message]
2008-11-20 21:24 ` [U-Boot] [PATCH]=?utf-8?q?rtc:=20add=20support=20for=204543=20RTC=20(manufactured=20by=20e.g.=20EPSON) Jean-Christophe PLAGNIOL-VILLARD
2008-11-20 21:46 ` [U-Boot] [PATCH] Hardware diagnosis for inka4x0 boards Jean-Christophe PLAGNIOL-VILLARD
2008-12-09 23:57 ` Wolfgang Denk
2008-12-11 15:28 ` Detlev Zundel
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=m2skouray9.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/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